From: syzbot <syzbot+246b47da27f8e7e7d6fb@syzkaller.appspotmail.com>
To: bfoster@redhat.com, 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 gc_bucket
Date: Thu, 06 Jun 2024 11:12:01 -0700 [thread overview]
Message-ID: <000000000000a05a05061a3c9e19@google.com> (raw)
In-Reply-To: <0000000000005221690619d26681@google.com>
syzbot has bisected this issue to:
commit 228e1c91ae5ec44f38aa8852aa3953005badce82
Author: Kent Overstreet <kent.overstreet@linux.dev>
Date: Wed Dec 27 23:31:46 2023 +0000
bcachefs: KEY_TYPE_accounting
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16a17f16980000
start commit: 0e1980c40b6e Add linux-next specific files for 20240531
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=15a17f16980000
console output: https://syzkaller.appspot.com/x/log.txt?x=11a17f16980000
kernel config: https://syzkaller.appspot.com/x/.config?x=d9c3ca4e54577b88
dashboard link: https://syzkaller.appspot.com/bug?extid=246b47da27f8e7e7d6fb
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11ca95fc980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12a49ef2980000
Reported-by: syzbot+246b47da27f8e7e7d6fb@syzkaller.appspotmail.com
Fixes: 228e1c91ae5e ("bcachefs: KEY_TYPE_accounting")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-06-06 18:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-01 11:28 [syzbot] [bcachefs?] kernel BUG in gc_bucket syzbot
2024-06-06 18:12 ` 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=000000000000a05a05061a3c9e19@google.com \
--to=syzbot+246b47da27f8e7e7d6fb@syzkaller.appspotmail.com \
--cc=bfoster@redhat.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