From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: fdmanana@kernel.org, fstests@vger.kernel.org
Cc: linux-btrfs@vger.kernel.org, Filipe Manana <fdmanana@suse.com>
Subject: Re: [PATCH] generic/363: mention btrfs kernel fix for block size < page size scenario
Date: Wed, 3 Sep 2025 07:13:24 +0930 [thread overview]
Message-ID: <98de454b-54ea-49da-92f1-95591fbf69d1@gmx.com> (raw)
In-Reply-To: <1d3740e7564f94ed51d18c4d53103624fb51e735.1756813886.git.fdmanana@suse.com>
在 2025/9/2 23:57, fdmanana@kernel.org 写道:
> From: Filipe Manana <fdmanana@suse.com>
>
> There's another btrfs kernel commit that landed in v6.16-rc1 and fixes
> another EOF truncation bug exposed by this test case, so add the commit
> in a _fixed_by_kernel_commit call.
>
> Signed-off-by: Filipe Manana <fdmanana@suse.com>
Reviewed-by: Qu Wenruo <wqu@suse.com>
Thanks,
Qu
> ---
> tests/generic/363 | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/tests/generic/363 b/tests/generic/363
> index 79b1ff89..f361878a 100755
> --- a/tests/generic/363
> +++ b/tests/generic/363
> @@ -13,8 +13,12 @@ _begin_fstest rw auto
>
> _require_test
>
> -[ $FSTYP == "btrfs" ] && _fixed_by_kernel_commit da2dccd7451d \
> - "btrfs: fix hole expansion when writing at an offset beyond EOF"
> +if [ $FSTYP == "btrfs" ]; then
> + _fixed_by_kernel_commit da2dccd7451d \
> + "btrfs: fix hole expansion when writing at an offset beyond EOF"
> + _fixed_by_kernel_commit 8e4f21f2b13d \
> + "btrfs: handle unaligned EOF truncation correctly for subpage cases"
> +fi
>
> # on failure, replace -q with -d to see post-eof writes in the dump output
> run_fsx "-q -S 0 -e 1 -N 100000"
prev parent reply other threads:[~2025-09-02 21:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 14:27 [PATCH] generic/363: mention btrfs kernel fix for block size < page size scenario fdmanana
2025-09-02 18:49 ` David Sterba
2025-09-02 21:43 ` 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=98de454b-54ea-49da-92f1-95591fbf69d1@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=fdmanana@kernel.org \
--cc=fdmanana@suse.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
/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