public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Baokun Li <libaokun1@huawei.com>
To: Alexander Mikhalitsyn <aleksandr.mikhalitsyn@canonical.com>,
	<fstests@vger.kernel.org>
Cc: <linux-ext4@vger.kernel.org>, <jack@suse.cz>, <tytso@mit.edu>,
	Yang Erkun <yangerkun@huawei.com>
Subject: Re: [PATCH] ext4/032: add a new testcase in online resize tests
Date: Sat, 9 Nov 2024 11:32:03 +0800	[thread overview]
Message-ID: <d137f247-97c0-4a42-b4ed-ae84ad8e727a@huawei.com> (raw)
In-Reply-To: <20241108134817.128078-1-aleksandr.mikhalitsyn@canonical.com>

Hi Alexander,

Thanks for the patch.

On 2024/11/8 21:48, Alexander Mikhalitsyn wrote:
> Add a new testcase for [1] commit in ext4 online resize testsuite.
>
> Link: https://lore.kernel.org/linux-ext4/20240927133329.1015041-1-libaokun@huaweicloud.com [1]
> Signed-off-by: Alexander Mikhalitsyn <aleksandr.mikhalitsyn@canonical.com>
> ---
>   tests/ext4/032 | 4 ++++
>   1 file changed, 4 insertions(+)
>
> diff --git a/tests/ext4/032 b/tests/ext4/032
> index 6bc3b61b..77d592f4 100755
> --- a/tests/ext4/032
> +++ b/tests/ext4/032
> @@ -97,6 +97,10 @@ mkdir -p $IMG_MNT || _fail "cannot create loopback mount point"
>   # Check if online resizing with bigalloc is supported by the kernel
>   ext4_online_resize 4096 8192 1
>   
> +_fixed_by_kernel_commit 6121258c2b33 \
> +	"ext4: fix off by one issue in alloc_flex_gd()"
> +ext4_online_resize $(c2b 6400) $(c2b 786432)
> +
I think this test would be better placed in the loop below. Then add some
comments describing the scenario being tested.

There are two current scenarios for off by one:
  * The above test is to expand from the first block group of a flex_bg to
    the next flex_bg;
  * Another scenario is to expand from the first block group of a flex_bg
    to the last block group of this flex_bg. For example,
      `ext4_online_resize $(c2b 6400) $(c2b 524288)`

In addition, we need to modify the tests/ext4/032.out or the use cases
will fail due to inconsistent output.


Regards,
Baokun
>   ## We perform resizing to various multiples of block group sizes to
>   ## ensure that we cover maximum edge cases in the kernel code.
>   for CLUSTER_SIZ in 4096 16384 65536; do



  reply	other threads:[~2024-11-09  3:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-08 13:48 [PATCH] ext4/032: add a new testcase in online resize tests Alexander Mikhalitsyn
2024-11-09  3:32 ` Baokun Li [this message]
2024-11-11 15:25   ` Aleksandr Mikhalitsyn
2024-11-14  3:04     ` Baokun Li
2024-11-09 12:01 ` Zorro Lang
2024-11-11 15:22   ` Aleksandr Mikhalitsyn

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=d137f247-97c0-4a42-b4ed-ae84ad8e727a@huawei.com \
    --to=libaokun1@huawei.com \
    --cc=aleksandr.mikhalitsyn@canonical.com \
    --cc=fstests@vger.kernel.org \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    --cc=yangerkun@huawei.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