linux-ext4 - Re: Mount option "noacl" will be removed by 3.5

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <6a320116-76a0-0562-3732-954002d40e45@redhat.com>
Date:   Sat, 7 Jan 2017 10:48:11 -0600
From:   Eric Sandeen <sandeen@...hat.com>
To:     Udo van den Heuvel <udovdh@...all.nl>, linux-ext4@...r.kernel.org
Subject: Re: Mount option "noacl" will be removed by 3.5

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

--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html