From: Eric Sandeen <sandeen@redhat.com>
To: Udo van den Heuvel <udovdh@xs4all.nl>, linux-ext4@vger.kernel.org
Subject: Re: Mount option "noacl" will be removed by 3.5
Date: Sat, 7 Jan 2017 10:48:11 -0600 [thread overview]
Message-ID: <6a320116-76a0-0562-3732-954002d40e45@redhat.com> (raw)
In-Reply-To: <fd36725d-d6d8-35a2-4f69-a3391aa4e42e@xs4all.nl>
On 1/7/17 7:14 AM, Udo van den Heuvel wrote:
> Hello!
>
> Why should it go?
> Found no explanation.
> What alternative is there to reduce unnecessary FS traffic?
It was a journey from not /requiring/ -o acl to use acls and
making it the default, to ultimately deprecating the noacl option.
The hope was that over the many years of the transition, anyone
who needed the old behavior would speak up. :)
You could always compile without CONFIG_EXT4_FS_POSIX_ACL if
you're really concerned about it. That's build time, not a
per-filesystem switch, of course.
If you have data to show that the inability to turn it off is
harmful, please share.
Thanks,
-Eric
> Kind regards,
> Udo
prev parent reply other threads:[~2017-01-07 16:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-07 13:14 Mount option "noacl" will be removed by 3.5 Udo van den Heuvel
2017-01-07 16:48 ` Eric Sandeen [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=6a320116-76a0-0562-3732-954002d40e45@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=udovdh@xs4all.nl \
/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