Bug 464682 – =dev-lang/v8-3.16.14.9-r1 fails with setfattr: Operation not supported

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Sergiy Borodych 2013-04-05 08:47:04 UTC]

Created attachment 344468 [details]
emerge -pqv '=dev-lang/v8-3.16.14.9-r1'

Build is ok, but failed on

... cut
 * XT PaX marking -me with setfattr
 *      out/x64.release/cctest
 *      out/x64.release/d8
 *      out/x64.release/shell
setfattr: out/x64.release/cctest: Operation not supported
setfattr: out/x64.release/d8: Operation not supported
setfattr: out/x64.release/shell: Operation not supported
 * Failed to set XATTR_PAX markings -me for:
 *      out/x64.release/shell
 * Executables may be killed by PaX kernels.
 * ERROR: dev-lang/v8-3.16.14.9-r1 failed (compile phase):
 *   (no error message)
... cut


# emerge -pqv '=dev-lang/v8-3.16.14.9-r1'
[ebuild  r  U ] dev-lang/v8-3.16.14.9-r1 [3.15.11.15]
[ebuild  r  U ] www-client/chromium-26.0.1410.43 [25.0.1364.160] USE="cups -bindist -custom-cflags -gnome -gnome-keyring -gps% -kerberos (-pulseaudio) (-selinux) (-system-ffmpeg) (-tcmalloc) {-test}" LINGUAS="ru uk -am -ar -bg -bn -ca -cs -da -de -el -en_GB -es -es_LA -et -fa -fi -fil -fr -gu -he -hi -hr -hu -id -it -ja -kn -ko -lt -lv -ml -mr -ms -nb -nl -pl -pt_BR -pt_PT -ro -sk -sl -sr -sv -sw -ta -te -th -tr -vi -zh_CN -zh_TW"

[Comment 1 Sergiy Borodych 2013-04-05 08:51:59 UTC]

# mount
...
/dev/mapper/vg-root on / type ext4 (rw,noatime,commit=0)
...

[Comment 2 Chí-Thanh Christopher Nguyễn 2013-04-05 09:05:13 UTC]

Can you attach the output of "tune2fs -l" of the filesystem that contains PORTAGE_TMPDIR?

[Comment 3 Dennis Schridde 2013-04-05 09:10:15 UTC]

Same happens for google-chrome:
>>> Install google-chrome-27.0.1453.15_beta191758 into /var/tmp/portage/www-client/google-chrome-27.0.1453.15_beta191758/image/ category www-client
 ^[[32;01m*^[[0m PT PaX marking -m with paxctl
 ^[[32;01m*^[[0m      opt/google/chrome/chrome
 ^[[32;01m*^[[0m XT PaX marking -me with setfattr
 ^[[32;01m*^[[0m      opt/google/chrome/chrome
setfattr: opt/google/chrome/chrome: Operation not supported
 ^[[33;01m*^[[0m Failed to set XATTR_PAX markings -me for:
 ^[[33;01m*^[[0m      opt/google/chrome/chrome
 ^[[33;01m*^[[0m Executables may be killed by PaX kernels.
 ^[[31;01m*^[[0m ERROR: www-client/google-chrome-27.0.1453.15_beta191758 failed (install phase):
 ^[[31;01m*^[[0m   (no error message)

/var/tmp/portage is a tmpfs with:
CONFIG_TMPFS=y
CONFIG_TMPFS_POSIX_ACL=y
CONFIG_TMPFS_XATTR=y
and:
none on /var/tmp/portage type tmpfs (rw,nosuid,nodev,relatime,size=4194304k,mode=1770,uid=250,gid=250)

But from the description of CONFIG_TMPFS_XATTR, not all namespaces are supported ("Currently this enables support for the trusted.* and security.* namespaces.").

[Comment 4 Dmitry 2013-04-05 09:13:19 UTC]

Have the same problem on x86 platform with reiserfs at PORTAGE_TMPDIR.

[Comment 5 Paolo Pedroni 2013-04-05 09:22:25 UTC]

*** Bug 464688 has been marked as a duplicate of this bug. ***

[Comment 6 Paolo Pedroni 2013-04-05 09:24:25 UTC]

It works if PORTAGE_TMPDIR is not on a tmpfs.

[Comment 7 Chí-Thanh Christopher Nguyễn 2013-04-05 09:30:20 UTC]

For those who have PORTAGE_TMPDIR on ext3/4 it may help to remount with user_xattr option.

[Comment 8 Agostino Sarubbo 2013-04-05 09:41:52 UTC]

(In reply to comment #6)
> It works if PORTAGE_TMPDIR is not on a tmpfs.

Worked here.

[Comment 9 Paolo Pedroni 2013-04-05 10:04:31 UTC]

(In reply to comment #8)
> Worked here.

May I ask you the mount options for your PORTAGE_TMPDIR, then? I may be missing something in mine.

[Comment 10 Paolo Pedroni 2013-04-05 10:18:12 UTC]

(In reply to comment #9)
> (In reply to comment #8)
> > Worked here.
> 
> May I ask you the mount options for your PORTAGE_TMPDIR, then? I may be
> missing something in mine.

If you run hardened gentoo (I don't), don't bother, I already found out that it supports user_xattr on tmpfs by default (http://blog.siphos.be/2012/12/another-hardened-month-has-passed/).

[Comment 11 Richard Freeman 2013-04-05 10:26:17 UTC]

Having same issue here.

CONFIG_TMPFS=y
CONFIG_TMPFS_POSIX_ACL=y
CONFIG_TMPFS_XATTR=y

tmpfs on /var/tmp type tmpfs (rw,size=5000m)

It appears that I cannot mount tmpfs with the user_xattr option - it doesn't appear on the manpage and dmesg contains the error:
tmpfs: No value for mount option 'user_xattr'

This is a non-hardened kernel/system.

[Comment 12 Sergiy Borodych 2013-04-05 10:28:15 UTC]

Created attachment 344484 [details]
tune2fs -l /dev/mapper/vg-root

(In reply to comment #2)
> Can you attach the output of "tune2fs -l" of the filesystem that contains
> PORTAGE_TMPDIR?

sure

[Comment 13 Agostino Sarubbo 2013-04-05 12:01:44 UTC]

(In reply to comment #9)
> (In reply to comment #8)
> > Worked here.
> 
> May I ask you the mount options for your PORTAGE_TMPDIR, then? I may be
> missing something in mine.

tmpfs on /tmp type tmpfs (rw,size=3300M,nr_inodes=1M)

and works also in another system:

/dev/sda1 on / type ext4 (rw,noatime,data=ordered)


@Sergiy: Could you try with the revision 1.18 of pax-utils.eclass ?

http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/eclass/pax-utils.eclass?revision=1.18

[Comment 14 Tomáš Chvátal (RETIRED) 2013-04-05 12:46:00 UTC]

Happens on tmpfs for me too.

And using the 1.18 eclass fixed the problem.

[Comment 15 Mike Gilbert 2013-04-05 14:36:37 UTC]

+  05 Apr 2013; Mike Gilbert <[e-mail]> -v8-3.15.11.15.ebuild,
+  -v8-3.16.14.2.ebuild, -v8-3.16.14.9.ebuild, v8-3.16.14.9-r1.ebuild:
+  Don't die on pax-mark failure, bug 464682.
+