All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: 李天宇 <lty218@stu.pku.edu.cn>
Cc: 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: Tue, 18 Nov 2025 22:06:49 -0800	[thread overview]
Message-ID: <aR1eeeCKE4AJSKwL@infradead.org> (raw)
In-Reply-To: <AA6A7gB4JrG-pMrNGmqTzap7.1.1763463974419.Hmail.2200013188@stu.pku.edu.cn>

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.

  reply	other threads:[~2025-11-19  6:06 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 [this message]
2025-11-19  6:41   ` Dave Chinner

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=aR1eeeCKE4AJSKwL@infradead.org \
    --to=hch@infradead.org \
    --cc=cem@kernel.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.