From: syzbot <syzbot+bcc38a9556d0324c2ec2@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, guoweikang.kernel@gmail.com,
kent.overstreet@linux.dev, kpsingh@kernel.org,
linux-bcachefs@vger.kernel.org, linux-kernel@vger.kernel.org,
mmpgouride@gmail.com, paulmck@kernel.org, pmladek@suse.com,
rrangel@chromium.org, syzkaller-bugs@googlegroups.com,
urezki@gmail.com, vbabka@suse.cz
Subject: Re: [syzbot] [bcachefs?] WARNING in rhashtable_init_noprof
Date: Tue, 27 May 2025 05:11:04 -0700 [thread overview]
Message-ID: <6835abd8.a70a0220.253bc2.00b0.GAE@google.com> (raw)
In-Reply-To: <68342b55.a70a0220.253bc2.0092.GAE@google.com>
syzbot has bisected this issue to:
commit 82067c916994dd1bfec65496144dc16e17899e36
Author: Kent Overstreet <kent.overstreet@linux.dev>
Date: Fri May 9 03:21:28 2025 +0000
bcachefs: buckets_in_flight on stack
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1528f882580000
start commit: 176e917e010c Add linux-next specific files for 20250523
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=1728f882580000
console output: https://syzkaller.appspot.com/x/log.txt?x=1328f882580000
kernel config: https://syzkaller.appspot.com/x/.config?x=e7902c752bef748
dashboard link: https://syzkaller.appspot.com/bug?extid=bcc38a9556d0324c2ec2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=145948e8580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13d6a170580000
Reported-by: syzbot+bcc38a9556d0324c2ec2@syzkaller.appspotmail.com
Fixes: 82067c916994 ("bcachefs: buckets_in_flight on stack")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-05-27 12:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-26 8:50 syzbot
2025-05-26 10:41 ` Alan Huang
2025-05-26 11:13 ` syzbot
2025-05-27 12:11 ` syzbot [this message]
2025-06-08 15:41 ` [syzbot] syzbot
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=6835abd8.a70a0220.253bc2.00b0.GAE@google.com \
--to=syzbot+bcc38a9556d0324c2ec2@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=guoweikang.kernel@gmail.com \
--cc=kent.overstreet@linux.dev \
--cc=kpsingh@kernel.org \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmpgouride@gmail.com \
--cc=paulmck@kernel.org \
--cc=pmladek@suse.com \
--cc=rrangel@chromium.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=urezki@gmail.com \
--cc=vbabka@suse.cz \
/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
Powered by JetHome