From: syzbot <syzbot+56edda805363e0a093b8@syzkaller.appspotmail.com>
To: kent.overstreet@linux.dev, linux-bcachefs@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bcachefs?] BUG: unable to handle kernel NULL pointer dereference in mempool_alloc_noprof (2)
Date: Sun, 01 Jun 2025 11:07:03 -0700 [thread overview]
Message-ID: <683c96c7.a00a0220.d8eae.0033.GAE@google.com> (raw)
In-Reply-To: <683bede4.a00a0220.d8eae.002a.GAE@google.com>
syzbot has bisected this issue to:
commit d4d71b58e5139afc5f9bda0139b99404eb216d8a
Author: Kent Overstreet <kent.overstreet@linux.dev>
Date: Sat Apr 5 21:36:04 2025 +0000
bcachefs: RO mounts now use less memory
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10914c82580000
start commit: 4cb6c8af8591 selftests/filesystems: Fix build of anon_inod..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=12914c82580000
console output: https://syzkaller.appspot.com/x/log.txt?x=14914c82580000
kernel config: https://syzkaller.appspot.com/x/.config?x=e413b6de2bc0230
dashboard link: https://syzkaller.appspot.com/bug?extid=56edda805363e0a093b8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11dd7ed4580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=113f9970580000
Reported-by: syzbot+56edda805363e0a093b8@syzkaller.appspotmail.com
Fixes: d4d71b58e513 ("bcachefs: RO mounts now use less memory")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-06-01 18:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-01 6:06 [syzbot] [bcachefs?] BUG: unable to handle kernel NULL pointer dereference in mempool_alloc_noprof (2) syzbot
2025-06-01 18:07 ` syzbot [this message]
2025-07-18 17:48 ` Kent Overstreet
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=683c96c7.a00a0220.d8eae.0033.GAE@google.com \
--to=syzbot+56edda805363e0a093b8@syzkaller.appspotmail.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/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