From: Aleksandr Nogikh <nogikh@google.com>
To: dsterba@suse.cz
Cc: syzbot <syzbot+3c4d8371d65230f852a2@syzkaller.appspotmail.com>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [btrfs?] BUG: corrupted list in btrfs_free_compr_folio
Date: Wed, 18 Mar 2026 23:05:06 +0100 [thread overview]
Message-ID: <CANp29Y7q2qyvCre5Una2vx3LM7g-0ZGpRmmT_R2BnnKqB_a4=A@mail.gmail.com> (raw)
In-Reply-To: <20260318163510.GE5735@twin.jikos.cz>
On Wed, Mar 18, 2026 at 5:35 PM David Sterba <dsterba@suse.cz> wrote:
>
> On Mon, Mar 16, 2026 at 06:40:28AM -0700, syzbot wrote:
> > Hello,
> >
> > syzbot found the following issue on:
> >
> > HEAD commit: f338e7738378 Linux 7.0-rc4
> > git tree: upstream
> > console output: https://syzkaller.appspot.com/x/log.txt?x=15265602580000
> > kernel config: https://syzkaller.appspot.com/x/.config?x=d46eab0cfd31c214
> > dashboard link: https://syzkaller.appspot.com/bug?extid=3c4d8371d65230f852a2
> > compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
> >
> > Unfortunately, I don't have any reproducer for this issue yet.
> >
> > Downloadable assets:
> > disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-f338e773.raw.xz
> > vmlinux: https://storage.googleapis.com/syzbot-assets/2567fb35ebfb/vmlinux-f338e773.xz
> > kernel image: https://storage.googleapis.com/syzbot-assets/f9124de81ddb/bzImage-f338e773.xz
> >
> > IMPORTANT: if you fix the issue, please add the following tag to the commit:
> > Reported-by: syzbot+3c4d8371d65230f852a2@syzkaller.appspotmail.com
>
> syz: fix: btrfs: zlib: handle page aligned compressed size correctly
#syz fix: btrfs: zlib: handle page aligned compressed size correctly
prev parent reply other threads:[~2026-03-18 22:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 13:40 [syzbot] [btrfs?] BUG: corrupted list in btrfs_free_compr_folio syzbot
2026-03-18 16:35 ` David Sterba
2026-03-18 22:05 ` Aleksandr Nogikh [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='CANp29Y7q2qyvCre5Una2vx3LM7g-0ZGpRmmT_R2BnnKqB_a4=A@mail.gmail.com' \
--to=nogikh@google.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+3c4d8371d65230f852a2@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