lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4be150fb-45c8-424f-84d0-378d2cdbc229@huawei.com>
Date: Thu, 14 Nov 2024 11:04:30 +0800
From: Baokun Li <libaokun1@...wei.com>
To: Aleksandr Mikhalitsyn <aleksandr.mikhalitsyn@...onical.com>
CC: <fstests@...r.kernel.org>, <linux-ext4@...r.kernel.org>, <jack@...e.cz>,
	<tytso@....edu>, Yang Erkun <yangerkun@...wei.com>
Subject: Re: [PATCH] ext4/032: add a new testcase in online resize tests

Hi Alexander,

On 2024/11/11 23:25, Aleksandr Mikhalitsyn wrote:
> On Sat, Nov 9, 2024 at 4:32 AM Baokun Li <libaokun1@...wei.com> wrote:
>> 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@...onical.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)
>>> +
> Hi Baokun,
>
>> I think this test would be better placed in the loop below. Then add some
>> comments describing the scenario being tested.
> Have done. Thanks!
Okay.
>> 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)`
> This test does not fail for me when I test without "ext4: fix off by
> one issue in alloc_flex_gd()" fix, so I decided not to take it.
Well, since we didn't check the off-by-one case directly, the latter case
really didn't cause the test case to fail before, and it doesn't appear
to have any effect at the moment, other than using some more memory.


Cheers,
Baokun

Powered by blists - more mailing lists