From: bugzilla-daemon@kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 215783] kernel NULL pointer dereference and general protection fault in fs/xfs/xfs_buf_item_recover.c: xlog_recover_do_reg_buffer() when mount a corrupted image
Date: Thu, 31 Mar 2022 21:35:45 +0000 [thread overview]
Message-ID: <bug-215783-201763-b5Tn4yr3RU@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215783-201763@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215783
--- Comment #1 from Dave Chinner (david@fromorbit.com) ---
On Thu, Mar 31, 2022 at 08:07:08PM +0000, bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=215783
> - Overview
> kernel NULL pointer dereference and general protection fault in
> fs/xfs/xfs_buf_item_recover.c:xlog_recover_do_reg_buffer() when mount a
> corrupted image, sometimes cause kernel hang
>
> - Reproduce
> tested on kernel 5.17.1, 5.15.32
>
> $ mkdir mnt
> $ unzip tmp7.zip
> $ ./mount.sh xfs 7 ##NULL pointer derefence
> or
> $ sudo mount -t xfs tmp7.img mnt ##general protection fault
>
> - Kernel dump
You've now raised 4 bugs that all look very similar and are quite
possibly all caused by the same corruption vector.
Please do some triage on the failure to identify the
source of the corruption that trigger this failure.
If you are going to run some scripted tool to randomly corrupt the
filesystem to find failures, then you have an ethical and moral
responsibility to do some of the work to narrow down and identify
the cause of the failure, not just throw them at someone to do all
the work.
You can automate this - track the corruptions you add to the
filesystem image, then when you have an image that reproduces a
problem, iterate over it removing corruptions until you have just
the minimum set of changes in the image that reproduce the issue.
Then you can cull all the images that trip over the same corruptions
and only report the actual corruption that causes the problem.
Then list those corruptions in the bug report so that we don't have
to do all this triage ourselves to weed out all the duplicates and
noise that all the random corruptions that don't cause crashes
induce.
-Dave.
--
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:[~2022-03-31 21:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 20:07 [Bug 215783] New: kernel NULL pointer dereference and general protection fault in fs/xfs/xfs_buf_item_recover.c: xlog_recover_do_reg_buffer() when mount a corrupted image bugzilla-daemon
2022-03-31 21:35 ` Dave Chinner
2022-03-31 23:17 ` Dave Chinner
2022-03-31 21:35 ` bugzilla-daemon [this message]
2022-03-31 23:17 ` [Bug 215783] " 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-215783-201763-b5Tn4yr3RU@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-xfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox