Re: XATTR_PAX, paxmark.sh, elog, icedtea, and maybe more
James Taylor <james-Lg6+em9gfQxWo+R/V/U2/[email protected]>
| Newsgroups | gmane.linux.gentoo.hardened |
|---|---|
| Message-ID | <[email protected]> |
On 2014/12/19 17:08, Karl-Johan Karlsson wrote: > On Thu 18 Dec 2014 19.58.11 Anthony G. Basile wrote: >> On 12/13/14 18:52, Karl-Johan Karlsson wrote: >>> So it works on ext4, but not ext3, even though both have the ext_attr flag >>> on disk. Any difference in kernel support? >> >> Because on ext3 you need to add user_xattr to the mount options. Either >> `mount -o user_xattr` or in fstab in column 4 like this >> >> /dev/sdb5 /tmp ext3 user_xattr 0 1 >> >> Its automatic on ext4. `man mount` for more info. Please let me know >> if this works for you. > > Aha! I was unaware of that mount option. mount(8) documents it, but is unclear > on what the default value is. attr(5) says it's needed on ext2, ext3 and > reiserfs, but says nothing about ext4. > > Unfortunately, the machine is in production, and since it works without that > option when using the ext4 code to read ext3, I would prefer to leave it alone > for now. Would mount -oremount,user_xattr be an option? Or am I missing the point :) P.S. Sorry for my garbled reply earlier, seems I'd forgotten to set Enigmail up properly.
signature.asc
(application/pgp-signature, 473 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJUk80AAAoJEHLy9B54fW4w8x8H/0A1akCq7rCevAPYHG0JoKI3 EaA7DQqJ8c6qe8RmUoUZb1cAhZUJaClJA5OsIf3RjLQ9cjlq0xwGhJpk/tP2Ru9x fKixd6O45VqVhqPM624k25IU2sFYMUoSaNk7h82AmQD6g+HA528wlLl1yLkojJKu W9W1bkwQ/xkzmgMcAUiNHfrhBxZt+CsJ3K45QlbYsA3LlvAMbfRi8mVq6QVuVNPP ozNK60e8fp+ZHRLsIsXo9RbQQ4KpS1Yr6YLkasFDfQVMzCNCaF9y0FKX+ZeCf9MI 0HkT45estcqL70yvKrzyoD8sFdpG5Nx576tVhpph1rHWRO+qRGd0US8Wg+L/jck= =MkOg -----END PGP SIGNATURE-----