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 [thread overview]
Message-ID: <bug-205197-13602-0dwx5XEBQm@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-205197-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=205197
--- 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 kernel 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 kernel
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 best
efforts basis, and when we have time, since after all, we're volunteers....
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2024-03-14 21:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-15 12:38 [Bug 205197] New: kernel BUG at fs/ext4/extents_status.c:884 bugzilla-daemon
2019-10-15 13:53 ` [Bug 205197] " bugzilla-daemon
2019-10-17 6:50 ` bugzilla-daemon
2019-10-23 13:13 ` bugzilla-daemon
2019-10-24 6:58 ` bugzilla-daemon
2024-03-04 4:17 ` bugzilla-daemon
2024-03-14 21:31 ` bugzilla-daemon [this message]
2024-03-15 12:14 ` bugzilla-daemon
2024-03-15 17:03 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-205197-13602-0dwx5XEBQm@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.