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]> |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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 :) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJUk8sJAAoJEHLy9B54fW4wGi8H/2eifOOUy8kkJAiUMALvOcUH aPloeW0ck52Zh0ZZ9qiuXYHJm30E1tNR6ymIihNYY1P8Uiimghv5IbvroMiraTzo bfjQEMXV/hcwNMsSTFLLNZWs2KDpIn36m/uJNjyUszZ5yUnrJVi4XrC7sMoiCcQb DrK24IFLrSmgM5+w0IPe35olHFXlJwQrJT/F+IjrMZkfHuWfl/eWVBPPqYsohv48 OaxWWYO33S5M3Vqr1rtCTeWQ2A/+saThewX5aZTtjaA4n8ZIW2khQuidXeUz/2kU /b8C9BN3ExtwUGHzmWV4W3dQVMdyGkfS/M0doF1TNo8IamfX2QPtKWc02siQ52k= =7vr7 -----END PGP SIGNATURE-----