From: syzbot <syzbot+997f0573004dcb964555@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?] kernel BUG in bch2_btree_path_traverse_one
Date: Thu, 14 Nov 2024 08:34:03 -0800 [thread overview]
Message-ID: <6736267b.050a0220.2a2fcc.0068.GAE@google.com> (raw)
In-Reply-To: <672b6e0d.050a0220.350062.024e.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=15abcb5f980000
start commit: f1b785f4c787 Merge tag 'for_linus' of git://git.kernel.org..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=17abcb5f980000
console output: https://syzkaller.appspot.com/x/log.txt?x=13abcb5f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=1503500c6f615d24
dashboard link: https://syzkaller.appspot.com/bug?extid=997f0573004dcb964555
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16172ce8580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=165214c0580000
Reported-by: syzbot+997f0573004dcb964555@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-14 16:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 13:24 [syzbot] [bcachefs?] kernel BUG in bch2_btree_path_traverse_one syzbot
2024-11-14 16:34 ` syzbot [this message]
2024-11-28 3:27 ` [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=6736267b.050a0220.2a2fcc.0068.GAE@google.com \
--to=syzbot+997f0573004dcb964555@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 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.