From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Mikhail Zaslonko <zaslonko@linux.ibm.com>,
Qu Wenruo <wqu@suse.com>, David Sterba <dsterba@suse.cz>,
linux-btrfs@vger.kernel.org
Cc: Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
Ilya Leoshkevich <iii@linux.ibm.com>,
linux-s390@vger.kernel.org
Subject: Re: [PATCH] btrfs: Fix avail_in bytes for s390 zlib HW compression path
Date: Fri, 13 Dec 2024 07:07:44 +1030 [thread overview]
Message-ID: <85bd7f9b-d9de-46ce-bda9-e7f2db31b8d6@gmx.com> (raw)
In-Reply-To: <20241212135000.1926110-1-zaslonko@linux.ibm.com>
在 2024/12/13 00:20, Mikhail Zaslonko 写道:
> Since the input data length passed to zlib_compress_folios() can be
> arbitrary, always setting strm.avail_in to a multiple of PAGE_SIZE may
> cause read-in bytes to exceed the input range. Currently this triggers
> an assert in btrfs_compress_folios() on the debug kernel. But it may
> potentially lead to data corruption.
Mind to provide the real world ASSERT() call trace?
AFAIK the range passed into btrfs_compress_folios() should always have
its start/length aligned to sector size.
Since s390 only supports 4K page size, that means the range is always
aligned to page size, and the existing code is also doing full page copy
anyway, thus I see no problem with the existing read.
Thanks,
Qu
> Fix strm.avail_in calculation for S390 hardware acceleration path.
>
> Signed-off-by: Mikhail Zaslonko <zaslonko@linux.ibm.com>
> Fixes: fd1e75d0105d ("btrfs: make compression path to be subpage compatible")
> ---
> fs/btrfs/zlib.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/btrfs/zlib.c b/fs/btrfs/zlib.c
> index ddf0d5a448a7..c9e92c6941ec 100644
> --- a/fs/btrfs/zlib.c
> +++ b/fs/btrfs/zlib.c
> @@ -174,10 +174,10 @@ int zlib_compress_folios(struct list_head *ws, struct address_space *mapping,
> copy_page(workspace->buf + i * PAGE_SIZE,
> data_in);
> start += PAGE_SIZE;
> - workspace->strm.avail_in =
> - (in_buf_folios << PAGE_SHIFT);
> }
> workspace->strm.next_in = workspace->buf;
> + workspace->strm.avail_in = min(bytes_left,
> + in_buf_folios << PAGE_SHIFT);
> } else {
> unsigned int pg_off;
> unsigned int cur_len;
next prev parent reply other threads:[~2024-12-12 20:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 13:50 [PATCH] btrfs: Fix avail_in bytes for s390 zlib HW compression path Mikhail Zaslonko
2024-12-12 15:37 ` Ilya Leoshkevich
2024-12-12 20:37 ` Qu Wenruo [this message]
2024-12-13 9:34 ` Zaslonko Mikhail
2024-12-13 9:42 ` 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=85bd7f9b-d9de-46ce-bda9-e7f2db31b8d6@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=agordeev@linux.ibm.com \
--cc=dsterba@suse.cz \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=iii@linux.ibm.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=wqu@suse.com \
--cc=zaslonko@linux.ibm.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