* Mount option "noacl" will be removed by 3.5
@ 2017-01-07 13:14 Udo van den Heuvel
2017-01-07 16:48 ` Eric Sandeen
0 siblings, 1 reply; 2+ messages in thread
From: Udo van den Heuvel @ 2017-01-07 13:14 UTC (permalink / raw)
To: linux-ext4
Hello!
Why should it go?
Found no explanation.
What alternative is there to reduce unnecessary FS traffic?
Kind regards,
Udo
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Mount option "noacl" will be removed by 3.5
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
0 siblings, 0 replies; 2+ messages in thread
From: Eric Sandeen @ 2017-01-07 16:48 UTC (permalink / raw)
To: Udo van den Heuvel, linux-ext4
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2017-01-07 16:48 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox