From: "xuyang2018.jy@fujitsu.com" <xuyang2018.jy@fujitsu.com>
To: Lukas Czerner <lczerner@redhat.com>
Cc: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] ext4: Remove deprecated flag for noacl and noxattr_user mount options
Date: Wed, 6 Jul 2022 10:05:14 +0000 [thread overview]
Message-ID: <62C56CA2.2050701@fujitsu.com> (raw)
In-Reply-To: <20220602110421.ymoug3rwfspmryqg@fedora>
on 2022/06/02 19:04, Lukas Czerner wrote:
> On Thu, Jun 02, 2022 at 06:01:39PM +0800, Yang Xu wrote:
>> Since kernel commit f70486055ee3 ("ext4: try to deprecate noacl and
>> noxattr_user mount options"), we deprecated these two mount options
>> because no other filesystem used the
>>
>> But now, acl has been used by ext4 ext2 btrfs f2fs ocfs2 and noxattr_user
>> has been used by ext4 ext2 f2fs ocfs2.
>
Firstly, sorry for this late reply. I am busy with other important thing
last month.
> And many other fs don't have it. Is that your only reason for dropping
> the deprecation?
YES.
> I can easily imagine that those fs got it because ext4
> had it at the time.
Maybe.
>
> Moreover the deprecation message has been there for 10 years, have we
> seen anyone actually complaining that they want to keep it?
I don't see any complains since 2018 because I start to test xfs/ext4
since that time
>
> Why not to just remove the option. I don't have a strong opinion either
> way, but it would be nice to remove stuff we don't need. Do you have a
> use case for it? If not, can we make it Opt_removed?
I don't have use case for it. OK, will send a remove patch tomorrow.
Best Regards
Yang Xu
>
> -Lukas
>
>>
>> I think it is time to remove deprecated flag for them.
>>
>> Signed-off-by: Yang Xu<xuyang2018.jy@fujitsu.com>
>> ---
>> fs/ext4/super.c | 4 ----
>> 1 file changed, 4 deletions(-)
>>
>> diff --git a/fs/ext4/super.c b/fs/ext4/super.c
>> index 450c918d68fc..8a0cc8815ee7 100644
>> --- a/fs/ext4/super.c
>> +++ b/fs/ext4/super.c
>> @@ -2116,10 +2116,6 @@ static int ext4_parse_param(struct fs_context *fc, struct fs_parameter *param)
>> else
>> return note_qf_name(fc, GRPQUOTA, param);
>> #endif
>> - case Opt_noacl:
>> - case Opt_nouser_xattr:
>> - ext4_msg(NULL, KERN_WARNING, deprecated_msg, param->key, "3.5");
>> - break;
>> case Opt_sb:
>> if (fc->purpose == FS_CONTEXT_FOR_RECONFIGURE) {
>> ext4_msg(NULL, KERN_WARNING,
>> --
>> 2.23.0
>>
>
prev parent reply other threads:[~2022-07-06 10:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 10:01 [PATCH] ext4: Remove deprecated flag for noacl and noxattr_user mount options Yang Xu
2022-06-02 11:04 ` Lukas Czerner
2022-07-06 10:05 ` xuyang2018.jy [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=62C56CA2.2050701@fujitsu.com \
--to=xuyang2018.jy@fujitsu.com \
--cc=lczerner@redhat.com \
--cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).