From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: 李天宇 <lty218@stu.pku.edu.cn>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-xfs <linux-xfs@vger.kernel.org>, cem <cem@kernel.org>
Subject: Re: [BUG] xfs: NULL pointer dereference in xfs_buf.h: xfs_buf_daddr()
Date: Wed, 19 Nov 2025 17:41:09 +1100 [thread overview]
Message-ID: <aR1mhcGvS7yxCG-R@dread.disaster.area> (raw)
In-Reply-To: <aR1eeeCKE4AJSKwL@infradead.org>
On Tue, Nov 18, 2025 at 10:06:49PM -0800, Christoph Hellwig wrote:
> On Tue, Nov 18, 2025 at 07:06:14PM +0800, 李天宇 wrote:
> > The kernel reports a kernel NULL pointer dereference when the sys_mount is called. This is triggered by the statement b_maps[0], where b_maps is NULL.
> >
> > This bug was discovered through a fuzzing framework on Linux v6.2
>
> Linux 6.2 is ancient (Feb 2023), and the buffer cache code has seen a
> major rewrite since:
>
> ch@brick:~/work/linux$ git diff v6.2..HEAD fs/xfs/xfs_buf.[ch] | diffstat
> xfs_buf.c | 1651 +++++++++++++++++++++++++++++++++++++++-----------------------------------------------------
> xfs_buf.h | 96 +++--
> 2 files changed, 768 insertions(+), 979 deletions(-)
>
> hch@brick:~/work/linux$ wc -l fs/xfs/xfs_buf.[ch]
> 2132 fs/xfs/xfs_buf.c
> 391 fs/xfs/xfs_buf.h
> 2523 total
>
> so I'm not sure how relevant this report is, especially without a good
> report.
It's not even a buffer cache bug. Something trashed a buffer
pointer in a btree cursor and xfs_buf_daddr() is the first
dereference to trip over it. It looks like random memory
corruption to me, so unless it is reproduced on a TOT kernel there's
no point spending any time looking at it...
-Dave.
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2025-11-19 6:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 11:06 [BUG] xfs: NULL pointer dereference in xfs_buf.h: xfs_buf_daddr() 李天宇
2025-11-19 6:06 ` Christoph Hellwig
2025-11-19 6:41 ` Dave Chinner [this message]
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=aR1mhcGvS7yxCG-R@dread.disaster.area \
--to=david@fromorbit.com \
--cc=cem@kernel.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=lty218@stu.pku.edu.cn \
/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.