From: syzbot <syzbot+c4614eae20a166c25bf0@syzkaller.appspotmail.com>
To: clm@fb.com, dsterba@suse.com, josef@toxicpanda.com,
linux-btrfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
wqu@suse.com
Subject: Re: [syzbot] [btrfs?] kernel BUG in assertfail (2)
Date: Thu, 20 Jul 2023 02:43:31 -0700 [thread overview]
Message-ID: <0000000000002f22130600e7fb01@google.com> (raw)
In-Reply-To: <000000000000f7b82505e9982685@google.com>
syzbot suspects this issue was fixed by commit:
commit 745806fb4554f334e6406fa82b328562aa48f08f
Author: Qu Wenruo <wqu@suse.com>
Date: Sun Jun 11 00:09:13 2023 +0000
btrfs: do not ASSERT() on duplicated global roots
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16d92676a80000
start commit: 830b3c68c1fb Linux 6.1
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=26d9ba6d9b746f4
dashboard link: https://syzkaller.appspot.com/bug?extid=c4614eae20a166c25bf0
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14078087880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1403948f880000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: btrfs: do not ASSERT() on duplicated global roots
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-07-20 9:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 17:49 [syzbot] kernel BUG in assertfail (2) syzbot
2023-07-20 9:43 ` syzbot [this message]
2023-07-20 9:46 ` [syzbot] [btrfs?] " Aleksandr Nogikh
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=0000000000002f22130600e7fb01@google.com \
--to=syzbot+c4614eae20a166c25bf0@syzkaller.appspotmail.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).