From: syzbot <syzbot+e8eff054face85d7ea41@syzkaller.appspotmail.com>
To: anupnewsmail@gmail.com, bfoster@redhat.com, devnull@kernel.org,
john@stoffel.org, kent.overstreet@linux.dev,
lihongbo22@huawei.com, linux-bcachefs@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org,
linux-kernel@vger.kernel.org, manas18244@iiitd.ac.in,
skhan@linuxfoundation.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bcachefs?] kernel BUG in bch2_dev_btree_bitmap_mark
Date: Sat, 02 Nov 2024 04:57:04 -0700 [thread overview]
Message-ID: <67261390.050a0220.3c8d68.0976.GAE@google.com> (raw)
In-Reply-To: <6716521c.050a0220.1e4b4d.005a.GAE@google.com>
syzbot has bisected this issue to:
commit 60f2b1bcf519416dbffee219132aa949d0c39d0e
Author: Kent Overstreet <kent.overstreet@linux.dev>
Date: Tue Apr 16 23:33:51 2024 +0000
bcachefs: Add asserts to bch2_dev_btree_bitmap_marked_sectors()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13d4cb40580000
start commit: 6c52d4da1c74 Merge tag 'for-linus' of git://git.kernel.org..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=1034cb40580000
console output: https://syzkaller.appspot.com/x/log.txt?x=17d4cb40580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f527353e21e067e8
dashboard link: https://syzkaller.appspot.com/bug?extid=e8eff054face85d7ea41
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14e972a7980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15ead340580000
Reported-by: syzbot+e8eff054face85d7ea41@syzkaller.appspotmail.com
Fixes: 60f2b1bcf519 ("bcachefs: Add asserts to bch2_dev_btree_bitmap_marked_sectors()")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-11-02 11:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-21 13:07 [syzbot] [bcachefs?] kernel BUG in bch2_dev_btree_bitmap_mark syzbot
2024-11-02 11:57 ` syzbot [this message]
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=67261390.050a0220.3c8d68.0976.GAE@google.com \
--to=syzbot+e8eff054face85d7ea41@syzkaller.appspotmail.com \
--cc=anupnewsmail@gmail.com \
--cc=bfoster@redhat.com \
--cc=devnull@kernel.org \
--cc=john@stoffel.org \
--cc=kent.overstreet@linux.dev \
--cc=lihongbo22@huawei.com \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manas18244@iiitd.ac.in \
--cc=skhan@linuxfoundation.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