From: Jan Kara <jack@suse.cz>
To: Patrik Schindler <poc@pocnet.net>
Cc: jack@suse.cz, linux-ext4@vger.kernel.org, Ted Tso <tytso@mit.edu>
Subject: Re: ext4: Remove deprecated noacl/nouser_xattr options
Date: Mon, 16 Jan 2023 11:42:54 +0100 [thread overview]
Message-ID: <20230116104254.xpphncpzu3zf53va@quack3> (raw)
In-Reply-To: <A5F622F8-99CF-4C7D-8811-7D82DB1C8846@pocnet.net>
Hello,
On Sun 15-01-23 23:56:21, Patrik Schindler wrote:
> sorry for contacting you directly, but I struggle to find relevant
> information on this topic.
This is best discussed on ext4 development mailing list (added to CC).
> In this web page is documented that "noacl" for ext4 is deprecated.
>
> https://patchwork.ozlabs.org/project/linux-ext4/patch/1658977369-2478-1-git-send-email-xuyang2018.jy@fujitsu.com/
>
> Do you have some background information at hand why noacl is deprecated,
> and how to get the functionality of noacl after this change?
Yes, these options were deprecated for a long time (10 years) and now they are
removed since nobody complained. The reasoning is in commit f70486055ee
("ext4: try to deprecate noacl and noxattr_user mount options"):
No other file system allows ACL's and extended attributes to be
enabled or disabled via a mount option. So let's try to deprecate
these options from ext4.
-
And it makes sense to me. It looks a bit strange and dangerous to disable
(part of) permission checks for the files. What usecase did you have for
it?
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next parent reply other threads:[~2023-01-16 10:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A5F622F8-99CF-4C7D-8811-7D82DB1C8846@pocnet.net>
2023-01-16 10:42 ` Jan Kara [this message]
2023-01-16 12:25 ` ext4: Remove deprecated noacl/nouser_xattr options Patrik Schindler
2023-01-17 10:45 ` Jan Kara
2023-01-17 10:55 ` Patrik Schindler
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=20230116104254.xpphncpzu3zf53va@quack3 \
--to=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=poc@pocnet.net \
--cc=tytso@mit.edu \
/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