From: Eric Biggers <ebiggers@kernel.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Bagas Sanjaya <bagasdotme@gmail.com>,
Pengfei Xu <pengfei.xu@intel.com>,
linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
heng.su@intel.com, dchinner@redhat.com, lkp@intel.com,
Linux Regressions <regressions@lists.linux.dev>
Subject: Re: [Syzkaller & bisect] There is BUG: unable to handle kernel NULL pointer dereference in xfs_extent_free_diff_items in v6.4-rc3
Date: Tue, 23 May 2023 00:00:29 +0000 [thread overview]
Message-ID: <20230523000029.GB3187780@google.com> (raw)
In-Reply-To: <20230522160525.GB11620@frogsfrogsfrogs>
On Mon, May 22, 2023 at 09:05:25AM -0700, Darrick J. Wong wrote:
> On Mon, May 22, 2023 at 01:39:27PM +0700, Bagas Sanjaya wrote:
> > On Mon, May 22, 2023 at 10:07:28AM +0800, Pengfei Xu wrote:
> > > Hi Darrick,
> > >
> > > Greeting!
> > > There is BUG: unable to handle kernel NULL pointer dereference in
> > > xfs_extent_free_diff_items in v6.4-rc3:
> > >
> > > Above issue could be reproduced in v6.4-rc3 and v6.4-rc2 kernel in guest.
> > >
> > > Bisected this issue between v6.4-rc2 and v5.11, found the problem commit is:
> > > "
> > > f6b384631e1e xfs: give xfs_extfree_intent its own perag reference
> > > "
> > >
> > > report0, repro.stat and so on detailed info is link: https://github.com/xupengfe/syzkaller_logs/tree/main/230521_043336_xfs_extent_free_diff_items
> > > Syzkaller reproduced code: https://github.com/xupengfe/syzkaller_logs/blob/main/230521_043336_xfs_extent_free_diff_items/repro.c
> > > Syzkaller reproduced prog: https://github.com/xupengfe/syzkaller_logs/blob/main/230521_043336_xfs_extent_free_diff_items/repro.prog
> > > Kconfig: https://github.com/xupengfe/syzkaller_logs/blob/main/230521_043336_xfs_extent_free_diff_items/kconfig_origin
> > > Bisect info: https://github.com/xupengfe/syzkaller_logs/blob/main/230521_043336_xfs_extent_free_diff_items/bisect_info.log
> > > Issue dmesg: https://github.com/xupengfe/syzkaller_logs/blob/main/230521_043336_xfs_extent_free_diff_items/v6.4-rc3_reproduce_dmesg.log
> > >
> > > v6.4-rc3 reproduced info:
>
> Diagnosis and patches welcomed.
>
> Or are we doing the usual syzbot bullshit where you all assume that I'm
> going to do all the fucking work for you?
>
It looks like Pengfei already took the time to manually bisect this issue to a
very recent commit authored by you. Is that not helpful?
(Apologies if I didn't include enough profanities for this email to be suitable
for linux-xfs@.)
- Eric
next prev parent reply other threads:[~2023-05-23 0:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 2:07 [Syzkaller & bisect] There is BUG: unable to handle kernel NULL pointer dereference in xfs_extent_free_diff_items in v6.4-rc3 Pengfei Xu
2023-05-22 6:39 ` Bagas Sanjaya
2023-05-22 16:05 ` Darrick J. Wong
2023-05-22 17:05 ` Linux regression tracking (Thorsten Leemhuis)
2023-05-23 6:08 ` Bagas Sanjaya
2023-05-23 6:44 ` Pengfei Xu
2023-05-23 0:00 ` Eric Biggers [this message]
2023-05-23 7:31 ` Dave Chinner
2023-05-23 9:14 ` Pengfei Xu
2023-05-23 21:52 ` Dave Chinner
2023-05-24 2:20 ` Pengfei Xu
2023-05-23 16:50 ` Eric Biggers
2023-05-23 22:16 ` Dave Chinner
2023-05-23 23:46 ` Eric Biggers
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=20230523000029.GB3187780@google.com \
--to=ebiggers@kernel.org \
--cc=bagasdotme@gmail.com \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=heng.su@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=lkp@intel.com \
--cc=pengfei.xu@intel.com \
--cc=regressions@lists.linux.dev \
/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.