From: "Darrick J. Wong" <djwong@kernel.org>
To: syzbot <syzbot+b9d2e54d2301324657ed@syzkaller.appspotmail.com>
Cc: boris@bur.io, clm@fb.com, dsterba@suse.com, fdmanana@suse.com,
josef@toxicpanda.com, linux-btrfs@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
wqu@suse.com
Subject: Re: [syzbot] [btrfs?] kernel BUG in set_state_bits
Date: Tue, 6 Aug 2024 15:18:45 -0700 [thread overview]
Message-ID: <20240806221845.GA623904@frogsfrogsfrogs> (raw)
In-Reply-To: <0000000000001e43de061f08c0d4@google.com>
On Tue, Aug 06, 2024 at 12:25:03PM -0700, syzbot wrote:
> syzbot suspects this issue was fixed by commit:
>
> commit 33336c1805d3a03240afda0bfb8c8d20395fb1d3
> Author: Boris Burkov <boris@bur.io>
> Date: Thu Jun 20 17:33:10 2024 +0000
>
> btrfs: preallocate ulist memory for qgroup rsv
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=165cd373980000
> start commit: 9fdfb15a3dbf Merge tag 'net-6.6-rc2' of git://git.kernel.o..
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=9681c105d52b0a72
> dashboard link: https://syzkaller.appspot.com/bug?extid=b9d2e54d2301324657ed
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=148ba274680000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14ff46c2680000
>
> If the result looks correct, please mark the issue as fixed by replying with:
>
> #syz fix: btrfs: preallocate ulist memory for qgroup rsv
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
I don't get it, why am I being cc'd on some random btrfs bug?
#syz check yourself before you wreck yourself
--D
next prev parent reply other threads:[~2024-08-06 22:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 12:20 [syzbot] kernel BUG in set_state_bits syzbot
2022-12-11 5:17 ` syzbot
2023-01-21 14:15 ` [syzbot] [btrfs?] " syzbot
2024-08-06 19:25 ` syzbot
2024-08-06 22:18 ` Darrick J. Wong [this message]
2024-08-06 22:18 ` syzbot
2024-08-07 11:33 ` David Sterba
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=20240806221845.GA623904@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=boris@bur.io \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=fdmanana@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+b9d2e54d2301324657ed@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=wqu@suse.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).