From: syzbot <syzbot+e4b5080f1e963225063e@syzkaller.appspotmail.com>
To: kent.overstreet@linux.dev, linux-bcachefs@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
terrelln@fb.com
Subject: Re: [syzbot] [bcachefs?] kernel BUG in bch2_fs_btree_write_buffer_exit
Date: Sat, 26 Oct 2024 00:13:04 -0700 [thread overview]
Message-ID: <671c9680.050a0220.2fdf0c.0224.GAE@google.com> (raw)
In-Reply-To: <66f76648.050a0220.46d20.002c.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=106e6f57980000
start commit: c2ee9f594da8 KVM: selftests: Fix build on on non-x86 archi..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=126e6f57980000
console output: https://syzkaller.appspot.com/x/log.txt?x=146e6f57980000
kernel config: https://syzkaller.appspot.com/x/.config?x=309bb816d40abc28
dashboard link: https://syzkaller.appspot.com/bug?extid=e4b5080f1e963225063e
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1218165f980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13d0a8a7980000
Reported-by: syzbot+e4b5080f1e963225063e@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-10-26 7:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-28 2:13 [syzbot] [bcachefs?] kernel BUG in bch2_fs_btree_write_buffer_exit syzbot
2024-10-25 2:12 ` syzbot
2024-10-26 7:13 ` syzbot [this message]
2024-11-08 3:04 ` [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=671c9680.050a0220.2fdf0c.0224.GAE@google.com \
--to=syzbot+e4b5080f1e963225063e@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 \
--cc=terrelln@fb.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