Received-SPF: pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Mon, 16 Jan 2023 11:42:54 +0100
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
Message-ID: <20230116104254.xpphncpzu3zf53va@quack3>
References: <A5F622F8-99CF-4C7D-8811-7D82DB1C8846@pocnet.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <A5F622F8-99CF-4C7D-8811-7D82DB1C8846@pocnet.net>
Precedence: bulk

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