From: Baokun Li <libaokun1@huawei.com>
To: Zorro Lang <zlang@kernel.org>
Cc: Theodore Ts'o <tytso@mit.edu>,
Ext4 Developers List <linux-ext4@vger.kernel.org>,
<fstests@vger.kernel.org>, <yangerkun@huawei.com>,
Baokun Li <libaokun1@huawei.com>
Subject: Re: [PATCH] ext4/059: disable block_validity checks when mounting a corrupted file system
Date: Sat, 22 Jun 2024 10:31:42 +0800 [thread overview]
Message-ID: <c26c4704-4f41-477d-a613-ec388536ea72@huawei.com> (raw)
In-Reply-To: <20240621163603.mid7acwta2tnbhqk@dell-per750-06-vm-08.rhts.eng.pek2.redhat.com>
On 2024/6/22 0:36, Zorro Lang wrote:
> On Thu, Jun 13, 2024 at 10:09:44AM +0800, Baokun Li wrote:
>> Hi Zorro,
>>
>> Could you pick up this patch?
>> This test case has been failing in the mainline for a while now.
> Sorry I just noticed this patch, looks like it was not sent to fstests@.
> Sure, I'll merge it, thanks for CC me :)
Thanks for merging it!
Seeing your reply I just noticed that the address of the fstests mail
list was misspelled.
Cheers,
Baokun
>
> Thanks,
> Zorro
>
>> Thanks,
>> Baokun
>>
>> On 2023/8/23 22:56, Theodore Ts'o wrote:
>>> Kernels with the commit "ext4: add correct group descriptors and
>>> reserved GDT blocks to system zone" will refuse to mount the corrupted
>>> file system constructed by this test. So in order to perform the
>>> test, we need to disable the block_validity checks.
>>>
>>> Signed-off-by: Theodore Ts'o <tytso@mit.edu>
>> Looks good to me, thanks for the patch!
>>
>> Reviewed-and-tested-by: Baokun Li <libaokun1@huawei.com>
>>
>>> ---
>>> tests/ext4/059 | 5 +++++
>>> 1 file changed, 5 insertions(+)
>>>
>>> diff --git a/tests/ext4/059 b/tests/ext4/059
>>> index 4230bde92..e4af77f1e 100755
>>> --- a/tests/ext4/059
>>> +++ b/tests/ext4/059
>>> @@ -31,6 +31,11 @@ $DEBUGFS_PROG -w -R "set_super_value s_reserved_gdt_blocks 100" $SCRATCH_DEV \
>>> $DEBUGFS_PROG -R "show_super_stats -h" $SCRATCH_DEV 2>/dev/null | \
>>> grep "Reserved GDT blocks"
>>> +# Kernels with the commit "ext4: add correct group descriptors and
>>> +# reserved GDT blocks to system zone" will refuse to mount the file
>>> +# system due to block_validity checks; so disable block_validity.
>>> +MOUNT_OPTIONS="$MOUNT_OPTIONS -o noblock_validity"
>>> +
>>> _scratch_mount
>>> # Expect no crash from this resize operation
>>>
prev parent reply other threads:[~2024-06-22 2:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 14:56 [PATCH] ext4/059: disable block_validity checks when mounting a corrupted file system Theodore Ts'o
2024-06-13 2:09 ` Baokun Li
2024-06-21 16:36 ` Zorro Lang
2024-06-22 2:31 ` Baokun Li [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=c26c4704-4f41-477d-a613-ec388536ea72@huawei.com \
--to=libaokun1@huawei.com \
--cc=fstests@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=yangerkun@huawei.com \
--cc=zlang@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;
as well as URLs for NNTP newsgroup(s).