From: David Sterba <dsterba@suse.cz>
To: syzbot <syzbot+34122898a11ab689518a@syzkaller.appspotmail.com>
Cc: clm@fb.com, dsterba@suse.com, josef@toxicpanda.com,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [btrfs?] kernel BUG in write_all_supers
Date: Thu, 27 Mar 2025 17:25:25 +0100 [thread overview]
Message-ID: <20250327162525.GU32661@twin.jikos.cz> (raw)
In-Reply-To: <67e5799e.050a0220.2f068f.0032.GAE@google.com>
On Thu, Mar 27, 2025 at 09:15:26AM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: f6e0150b2003 Merge tag 'mtd/for-6.15' of git://git.kernel...
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=1405d804580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=46a07195688b794b
> dashboard link: https://syzkaller.appspot.com/bug?extid=34122898a11ab689518a
> compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10d7abb0580000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15d76198580000
>
> Downloadable assets:
> disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7feb34a89c2a/non_bootable_disk-f6e0150b.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/7ade4c34c9b1/vmlinux-f6e0150b.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/1fe37b97ec9d/bzImage-f6e0150b.xz
> mounted in repro: https://storage.googleapis.com/syzbot-assets/1f4c759fe772/mount_0.gz
> fsck result: OK (log: https://syzkaller.appspot.com/x/fsck.log?x=1757abb0580000)
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+34122898a11ab689518a@syzkaller.appspotmail.com
>
> BTRFS info (device loop0): using sha256 (sha256-avx2) checksum algorithm
> BTRFS info (device loop0): using free-space-tree
> assertion failed: folio_order(folio) == 0, in fs/btrfs/disk-io.c:3858
This is
ASSERT(folio_order(folio) == 0);
and the folio is from device->bdev->bd_mapping.
next prev parent reply other threads:[~2025-03-27 16:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-27 16:15 syzbot
2025-03-27 16:25 ` David Sterba [this message]
2025-03-27 21:04 ` Qu Wenruo
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=20250327162525.GU32661@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+34122898a11ab689518a@syzkaller.appspotmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®