From: Qu Wenruo <wqu@suse.com>
To: Weiming Shi <bestswngs@gmail.com>,
David Sterba <dsterba@suse.com>, Chris Mason <clm@fb.com>
Cc: Xiang Mei <xmei5@asu.edu>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] btrfs: lzo: reject compressed segment that overflows the compressed input
Date: Sun, 7 Jun 2026 15:42:52 +0930 [thread overview]
Message-ID: <e8cf9678-f746-4184-9f0c-cb3415845537@suse.com> (raw)
In-Reply-To: <20260607052511.4131138-3-bestswngs@gmail.com>
在 2026/6/7 14:55, Weiming Shi 写道:
> lzo_decompress_bio() validates each on-disk segment length seg_len only
> against the workspace cbuf size, not against the compressed input size
> (compressed_len, the total folio bytes of the bio). A crafted extent can
> carry a segment whose seg_len passes the cbuf check but runs past the end
> of the bio, so copy_compressed_segment() walks off the last folio:
> get_current_folio() then returns the NULL folio from bio_next_folio(), and
> with CONFIG_BTRFS_ASSERT disabled (default) folio_size(NULL) faults.
>
> BUG: KASAN: null-ptr-deref in lzo_decompress_bio (fs/btrfs/lzo.c:383)
> Read of size 8 at addr 0000000000000000 by task kworker/u8:1/29
> Workqueue: btrfs-endio simple_end_io_work
> kasan_report (mm/kasan/report.c:590)
> lzo_decompress_bio (fs/btrfs/lzo.c:383)
> end_bbio_compressed_read (fs/btrfs/compression.c:1065)
> btrfs_bio_end_io (fs/btrfs/bio.c:135)
> btrfs_check_read_bio (fs/btrfs/bio.c:180 fs/btrfs/bio.c:285)
> simple_end_io_work
> process_one_work
> worker_thread
>
> Reject any segment whose payload would extend beyond compressed_len before
> copying it, treating it as corruption like the other on-disk validation
> failures in this function.
>
> Fixes: a6e66e6f8c1b ("btrfs: rework lzo_decompress_bio() to make it subpage compatible")
> Reported-by: Xiang Mei <xmei5@asu.edu>
> Assisted-by: Claude:claude-opus-4-8
> Signed-off-by: Weiming Shi <bestswngs@gmail.com>
Reviewed-by: Qu Wenruo <wqu@suse.com>
And pushed to for-next.
Thanks,
Qu
> ---
> v2:
> - Return -EUCLEAN instead of -EIO to match lzo_decompress() (Qu Wenruo).
> - Emit a btrfs_err() message when rejecting the segment (Qu Wenruo).
>
> fs/btrfs/lzo.c | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/fs/btrfs/lzo.c b/fs/btrfs/lzo.c
> index 2de18c7b5..6e4aa2285 100644
> --- a/fs/btrfs/lzo.c
> +++ b/fs/btrfs/lzo.c
> @@ -491,6 +491,17 @@ int lzo_decompress_bio(struct list_head *ws, struct compressed_bio *cb)
> return -EIO;
> }
>
> + /* The segment must not extend beyond the compressed input. */
> + if (unlikely(cur_in + seg_len > compressed_len)) {
> + struct btrfs_inode *inode = cb->bbio.inode;
> +
> + btrfs_err(fs_info,
> + "lzo segment overflows compressed input, root %llu inode %llu offset %llu cur_in %u len %u compressed len %u",
> + btrfs_root_id(inode->root), btrfs_ino(inode),
> + cb->start, cur_in, seg_len, compressed_len);
> + return -EUCLEAN;
> + }
> +
> /* Copy the compressed segment payload into workspace */
> copy_compressed_segment(cb, &fi, &cur_folio_index, workspace->cbuf,
> seg_len, &cur_in);
prev parent reply other threads:[~2026-06-07 6:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-07 5:25 Weiming Shi
2026-06-07 6:12 ` Qu Wenruo [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=e8cf9678-f746-4184-9f0c-cb3415845537@suse.com \
--to=wqu@suse.com \
--cc=bestswngs@gmail.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xmei5@asu.edu \
/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®