From: "xuyang2018.jy@fujitsu.com" <xuyang2018.jy@fujitsu.com>
To: Zorro Lang <zlang@redhat.com>
Cc: "fstests@vger.kernel.org" <fstests@vger.kernel.org>,
"jack@suse.cz" <jack@suse.cz>,
"oliver.sang@intel.com" <oliver.sang@intel.com>,
"lkp@intel.com" <lkp@intel.com>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
"tytso@mit.edu" <tytso@mit.edu>,
"lczerner@redhat.com" <lczerner@redhat.com>
Subject: Re: [PATCH] ext4/053: Remove nouser_xattr test
Date: Mon, 29 Aug 2022 01:07:24 +0000 [thread overview]
Message-ID: <1ac7f566-5880-7060-bd24-0637ccc1258c@fujitsu.com> (raw)
In-Reply-To: <20220828024858.cf5awn2uksbpchb3@zlang-mailbox>
on 2022/08/28 10:48, Zorro Lang wrote:
> On Wed, Aug 17, 2022 at 11:10:23AM +0800, Yang Xu wrote:
>> Plan to remove noacl and nouser_xattr mount option in kernel because they
>> are deprecated[1]. So remove nouser_xattr test in here.
>
> What's the [1]?
>
> We'd better to be careful when we want to remove a testing coverage. I'm not
> sure if they've decided to removed this mount option, the ext4/053 is an
> important test case for ext4, so I'd like to hear their opinion.
Sorry for this miss.
[1]https://lore.kernel.org/linux-ext4/1658977369-2478-1-git-send-email-xuyang2018.jy@fujitsu.com/T/#t
Best Regards
Yang Xu
>
> Thanks,
> Zorro
>
>>
>> Reported-by: kernel test robot <oliver.sang@intel.com>
>> Signed-off-by: Yang Xu <xuyang2018.jy@fujitsu.com>
>> ---
>> tests/ext4/053 | 1 -
>> 1 file changed, 1 deletion(-)
>>
>> diff --git a/tests/ext4/053 b/tests/ext4/053
>> index 555e474e..5d2c478a 100755
>> --- a/tests/ext4/053
>> +++ b/tests/ext4/053
>> @@ -439,7 +439,6 @@ for fstype in ext2 ext3 ext4; do
>> mnt oldalloc removed
>> mnt orlov removed
>> mnt -t user_xattr
>> - mnt nouser_xattr
>>
>> if _has_kernel_config CONFIG_EXT4_FS_POSIX_ACL; then
>> mnt -t acl
>> --
>> 2.27.0
>>
>
next prev parent reply other threads:[~2022-08-29 1:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 3:10 [PATCH] ext4/053: Remove nouser_xattr test Yang Xu
2022-08-28 2:48 ` Zorro Lang
2022-08-29 1:07 ` xuyang2018.jy [this message]
2022-08-29 10:06 ` Jan Kara
2022-08-31 9:31 ` Zorro Lang
2022-08-31 10:37 ` Jan Kara
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=1ac7f566-5880-7060-bd24-0637ccc1258c@fujitsu.com \
--to=xuyang2018.jy@fujitsu.com \
--cc=fstests@vger.kernel.org \
--cc=jack@suse.cz \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oliver.sang@intel.com \
--cc=tytso@mit.edu \
--cc=zlang@redhat.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