From: syzbot <syzbot+aa930d41d2f32904c5da@syzkaller.appspotmail.com>
To: axboe@kernel.dk, cem@kernel.org, clm@fb.com, djwong@kernel.org,
dsterba@suse.com, josef@toxicpanda.com,
kent.overstreet@linux.dev, linux-bcachefs@vger.kernel.org,
linux-block@vger.kernel.org, linux-btrfs@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bcachefs?] general protection fault in put_pwq_unlocked (2)
Date: Thu, 19 Dec 2024 08:50:02 -0800 [thread overview]
Message-ID: <67644eba.050a0220.1e8afc.0001.GAE@google.com> (raw)
In-Reply-To: <6714a705.050a0220.1e4b4d.0035.GAE@google.com>
syzbot has bisected this issue to:
commit 62719cf33c3ad62986130a19496cd864a0ed06c3
Author: Kent Overstreet <kent.overstreet@linux.dev>
Date: Sat Dec 23 22:50:29 2023 +0000
bcachefs: Fix nochanges/read_only interaction
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17a4f7e8580000
start commit: eabcdba3ad40 Merge tag 'for-6.13-rc3-tag' of git://git.ker..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=1464f7e8580000
console output: https://syzkaller.appspot.com/x/log.txt?x=1064f7e8580000
kernel config: https://syzkaller.appspot.com/x/.config?x=1234f097ee657d8b
dashboard link: https://syzkaller.appspot.com/bug?extid=aa930d41d2f32904c5da
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16dc4cf8580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12faef44580000
Reported-by: syzbot+aa930d41d2f32904c5da@syzkaller.appspotmail.com
Fixes: 62719cf33c3a ("bcachefs: Fix nochanges/read_only interaction")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
parent reply other threads:[~2024-12-19 16:50 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <6714a705.050a0220.1e4b4d.0035.GAE@google.com>]
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=67644eba.050a0220.1e8afc.0001.GAE@google.com \
--to=syzbot+aa930d41d2f32904c5da@syzkaller.appspotmail.com \
--cc=axboe@kernel.dk \
--cc=cem@kernel.org \
--cc=clm@fb.com \
--cc=djwong@kernel.org \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@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;
as well as URLs for NNTP newsgroup(s).