From: syzbot <syzbot+88247ec7a18c953867d5@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
Subject: Re: [syzbot] [btrfs?] WARNING in do_chunk_alloc
Date: Sun, 10 Sep 2023 20:20:33 -0700 [thread overview]
Message-ID: <00000000000029cdd406050ccfff@google.com> (raw)
In-Reply-To: <000000000000fcf6d705ee1d8947@google.com>
syzbot suspects this issue was fixed by commit:
commit cd361199ff23776481c37023a55d855d5ad5c0f5
Author: Josef Bacik <josef@toxicpanda.com>
Date: Mon Jul 31 20:28:43 2023 +0000
btrfs: wait on uncached block groups on every allocation loop
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1582bf14680000
start commit: eb7081409f94 Linux 6.1-rc6
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=8cdf448d3b35234
dashboard link: https://syzkaller.appspot.com/bug?extid=88247ec7a18c953867d5
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10b80ab1880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12dd6d45880000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: btrfs: wait on uncached block groups on every allocation loop
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-09-11 3:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 6:38 [syzbot] WARNING in do_chunk_alloc syzbot
2023-09-11 3:20 ` syzbot [this message]
2023-09-13 14:03 ` [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=00000000000029cdd406050ccfff@google.com \
--to=syzbot+88247ec7a18c953867d5@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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.