From: syzbot <syzbot+e22007d6acb9c87c2362@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?] general protection fault in bch2_btree_path_traverse_one
Date: Thu, 07 Nov 2024 14:15:03 -0800 [thread overview]
Message-ID: <672d3be7.050a0220.0db4.01af.GAE@google.com> (raw)
In-Reply-To: <671b3f3e.050a0220.2eb763.00d4.GAE@google.com>
syzbot has bisected this issue to:
commit bf4baaa087e2be0279991f1dbf9acaa7a4c9148c
Author: Kent Overstreet <kent.overstreet@linux.dev>
Date: Sat Oct 5 21:37:02 2024 +0000
bcachefs: Fix lockdep splat in bch2_accounting_read
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1102fd5f980000
start commit: ff7afaeca1a1 Merge tag 'nfs-for-6.12-3' of git://git.linux..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=1302fd5f980000
console output: https://syzkaller.appspot.com/x/log.txt?x=1502fd5f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=921b01cbfd887a9b
dashboard link: https://syzkaller.appspot.com/bug?extid=e22007d6acb9c87c2362
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14d9ae30580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13003f40580000
Reported-by: syzbot+e22007d6acb9c87c2362@syzkaller.appspotmail.com
Fixes: bf4baaa087e2 ("bcachefs: Fix lockdep splat in bch2_accounting_read")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-11-07 22:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 6:48 [syzbot] [bcachefs?] general protection fault in bch2_btree_path_traverse_one syzbot
2024-11-07 22:15 ` syzbot [this message]
2024-11-27 8:09 ` [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=672d3be7.050a0220.0db4.01af.GAE@google.com \
--to=syzbot+e22007d6acb9c87c2362@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