-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I came across a debian bug report and confirmed that when you remount
- -o acl, dmesg shows ext4 acknowledging the remount with the acl
option, but /proc/mounts does not show the acl option. Is this a
kernel bug or is it intentional?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJS85spAAoJEI5FoCIzSKrwBw4IAKX9QSn4P6F8k1q8YqFzNvGD
F4nuE4y54N0oGWmb1wXn0T0v2c0dWomJSN8QgqMUgfTWPy4vN9KTLJFK6xCZNP21
5PtAVe4SGKfXTLWWGAYpZAf50TH7Qxigos3Wcgfzi6YeZ8vu4U8I7eBMFBPe5uO7
XoYQYUKEZWTpO1RxxeQWEt2OBVnjAMssmE+Hi05t5/Q1kbGQCCIZe2QlGkLLspya
PIk3TViA6ZFtm7em6nUnNFTg+LRigyfF3+X51uUx+RGK8ljDhbWO1TGC5XUFigyX
aWrF6BGuT09I06QVeIBzpp5hiR353vkOV3ILcDfmQmUmsHWEsnV9+NKW/x3LusY=
=HSoQ
-----END PGP SIGNATURE-----
On Thu, Feb 06, 2014 at 09:24:41AM -0500, Phillip Susi wrote:
> I came across a debian bug report and confirmed that when you remount
> - -o acl, dmesg shows ext4 acknowledging the remount with the acl
> option, but /proc/mounts does not show the acl option. Is this a
> kernel bug or is it intentional?
The acl mount option is now defaulted on, so it's not a bug that if
you specify the acl option, it won't get displayed in /proc/mounts.
What *is* a bug is that if you specify "mount -o noacl", that doesn't
show up in /proc/mounts.
Cheers,
- Ted