From: syzbot <syzbot+e8e56d5d31d38b5b47e7@syzkaller.appspotmail.com>
To: alfredidavidson@usa.com, anamartinez@projectloan.org,
anand.jain@oracle.com, brauner@kernel.org, clm@fb.com,
dsterba@suse.com, dvyukov@google.com, fdmanana@kernel.org,
franklinozil@usa.com, inquiry@usa.com,
johannes.thumshirn@wdc.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 btrfs_chunk_alloc
Date: Sat, 20 Apr 2024 04:05:03 -0700 [thread overview]
Message-ID: <000000000000146a6a0616852ded@google.com> (raw)
In-Reply-To: <00000000000089deb205ee0ddd58@google.com>
syzbot suspects this issue was fixed by commit:
commit a1912f712188291f9d7d434fba155461f1ebef66
Author: Josef Bacik <josef@toxicpanda.com>
Date: Wed Nov 22 17:17:55 2023 +0000
btrfs: remove code for inode_cache and recovery mount options
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=123666bf180000
start commit: 82714078aee4 Merge tag 'pm-6.6-rc5' of git://git.kernel.or..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=7a5682d32a74b423
dashboard link: https://syzkaller.appspot.com/bug?extid=e8e56d5d31d38b5b47e7
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=139f64ee680000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12da37d1680000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: btrfs: remove code for inode_cache and recovery mount options
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-04-20 11:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 11:56 [syzbot] WARNING in btrfs_chunk_alloc syzbot
2022-11-22 14:59 ` Filipe Manana
2022-11-22 17:42 ` Dmitry Vyukov
2024-04-20 11:05 ` 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=000000000000146a6a0616852ded@google.com \
--to=syzbot+e8e56d5d31d38b5b47e7@syzkaller.appspotmail.com \
--cc=alfredidavidson@usa.com \
--cc=anamartinez@projectloan.org \
--cc=anand.jain@oracle.com \
--cc=brauner@kernel.org \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=dvyukov@google.com \
--cc=fdmanana@kernel.org \
--cc=franklinozil@usa.com \
--cc=inquiry@usa.com \
--cc=johannes.thumshirn@wdc.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.