Received-SPF: pass (google.com: domain of linux-ext4+bounces-1654-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1;
From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 205197] kernel BUG at fs/ext4/extents_status.c:884
Date: Thu, 14 Mar 2024 21:31:47 +0000
Message-ID: <bug-205197-13602-0dwx5XEBQm@https.bugzilla.kernel.org/>
In-Reply-To: <bug-205197-13602@https.bugzilla.kernel.org/>
References: <bug-205197-13602@https.bugzilla.kernel.org/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Auto-Submitted: auto-generated
Precedence: bulk
MIME-Version: 1.0

https://bugzilla.kernel.org/show_bug.cgi?id=3D205197

--- Comment #6 from Theodore Tso (tytso@mit.edu) ---
The reason why no one has paid much attention to it is because the bug is
reported against a very old kernel, and upstream developers generally only
worry about the upstream kernel.  Companies which insist on using old stable
kernels need to either engage paid support (e.g., contacting Red Hat if you=
 are
using RHEL, etc.) or have their own kernel developers on staff to debug the
problem.  Upstream developers are volunteers don't have the time to provide
free support to companies that are using old kernels.  In general, at the
minimum we ask kernel engineers working on these kernels to try to reproduce
the problem on the latest upstream kernel, and if they can't.... maybe they
should work on using a newer upstream kernel, or they should figure out how=
 to
backport fixes to old LTS kernels.

Also, it seems... weird.... that you can't look at the hex dump.  The kerne=
l is
able to mount the kernel, so you have access to the encryption key, or at
least, to a block device which has the encryption key set up by your user
space.   So you should be able to run e2fsck -fn /dev/hdXX.  This would help
provide a hint to the nature of the corruption, so that we could try to
reproduce the problem on an upstream kernel.   But what we really don't have
time to do is to hand-hold users who don't know how to run fsck or apply ke=
rnel
patches, and trying to run test kernels.

If you can let us know what you actually can do, perhaps we might bend the
rules and try to give you some debugging help.  But it will only be on a be=
st
efforts basis, and when we have time, since after all, we're volunteers....

--=20
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.=