From: syzbot <syzbot+6e54e639e7b934d64304@syzkaller.appspotmail.com>
To: brauner@kernel.org, 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?] WARNING in btrfs_finish_one_ordered
Date: Sat, 08 Nov 2025 00:13:02 -0800 [thread overview]
Message-ID: <690efb8e.a70a0220.22f260.0078.GAE@google.com> (raw)
In-Reply-To: <000000000000804fb406009d9880@google.com>
syzbot suspects this issue was fixed by commit:
commit 736bd9d2e35866a07f32d9884019e0431b0b50d8
Author: Qu Wenruo <wqu@suse.com>
Date: Fri Jul 4 09:38:03 2025 +0000
btrfs: restrict writes to opened btrfs devices
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13ecb812580000
start commit: 374a7f47bf40 Merge tag '6.5-rc5-ksmbd-server' of git://git..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=da6e201fec031cc0
dashboard link: https://syzkaller.appspot.com/bug?extid=6e54e639e7b934d64304
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17eef89da80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=147c2fa5a80000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: btrfs: restrict writes to opened btrfs devices
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-11-08 8:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-16 16:58 [syzbot] [btrfs?] WARNING in btrfs_finish_one_ordered syzbot
2023-08-10 18:40 ` syzbot
2025-11-08 8:13 ` 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=690efb8e.a70a0220.22f260.0078.GAE@google.com \
--to=syzbot+6e54e639e7b934d64304@syzkaller.appspotmail.com \
--cc=brauner@kernel.org \
--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