public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: [rfc] enable USE=xattr by default
Date: Thu, 15 Oct 2015 12:07:00 +0000 (UTC)	[thread overview]
Message-ID: <pan$4526d$f94981d4$9f9a22cc$1e2e87bb@cox.net> (raw)
In-Reply-To: 20151015140929.40f44daa@laptop.puleglot.ru

Alexander Tsoy posted on Thu, 15 Oct 2015 14:09:29 +0300 as excerpted:

> On Thu, 15 Oct 2015 18:56:28 +0800 Jason Zaman <perfinion@gentoo.org>
> wrote:
> 
>> On Thu, Oct 15, 2015 at 10:57:45AM +0200, Tobias Klausmann wrote:
>> > Hi!
>> > 
>> > On Wed, 14 Oct 2015, Mike Frysinger wrote:
>> > > anyone opposed to flipping this flag on by default ?
>> > > 
>> > > reference:
>> > > https://bugs.gentoo.org/506198 https://bugs.gentoo.org/556408
>> > 
>> > No objection, but a bit of a datapoint. I use btrfs on one of my
>> > machines, and that filesystem (apparently) does not support XATTR_PAX
>> > markings. So on every update I get some packages with message like
>> > these:
>> 
>> I used to run hardened on btrfs and it worked fine. pax xattrs are in
>> the user namespace (user.pax.flags) which isnt protected (unlike eg.
>> security.*). I dont remember doing anything special to enable xattrs on
>> btrfs, most of the newer FSs have them enabled by default.
>> 
>> Can you try this:
>> 
>> # getfattr -d -m- /bin/ping
> 
> I think he should check xattr support in PORTAGE_TMPDIR in the first
> place. :) I suspect something like tmpfs mounted on it (and
> CONFIG_TMPFS_XATTR=n in the kernel config).

As I posted, I have the same problem here (tho I didn't blame btrfs), but 
while PORTAGE_TMPDIR is indeed tmpfs, zgrep XATTR /proc/config.gz says 
CONFIG_TMPFS_XATTR=y, so that's not it.

But the closest thing btrfs has to that option is 
CONFIG_BTRFS_FS_POSIX_ACL, which I do NOT have enabled, so if it's 
required...

Meanwhile, the setfattr/getfattr test works (tho getfattr says it's 
removing the leading /).  So it would appear btrfs is fine, and the tmpfs 
PORTAGE_TMPDIR is fine, but I still get those XATTR_PAX failed-to-set 
warnings.

Tho I just remerged iputils and didn't get the warnings, so maybe we're 
not checking the right binaries?

IIRC, firefox gave me the warnings, however, and I'm doing an update 
including 41.0.1 ATM, so I can verify, tho of course FF takes awhile to 
build and it's near the end of a list of 100+ packages to update, so...

Could it be related to one of FEATURES="ipc-sandbox sandbox userpriv 
usersandbox xattr" (choosing a few from my set that look like possible 
candidates)?

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman



  reply	other threads:[~2015-10-15 12:07 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-15  3:48 [gentoo-dev] [rfc] enable USE=xattr by default Mike Frysinger
2015-10-15  4:41 ` Jason Zaman
2015-10-15  8:57 ` Tobias Klausmann
2015-10-15 10:32   ` [gentoo-dev] " Duncan
2015-10-15 11:36     ` Anthony G. Basile
2015-10-15 10:56   ` [gentoo-dev] " Jason Zaman
2015-10-15 11:09     ` Alexander Tsoy
2015-10-15 12:07       ` Duncan [this message]
2015-10-15 11:22     ` Tobias Klausmann
2015-10-15 11:49       ` Rich Freeman
2015-10-15 11:24     ` Rich Freeman
2015-10-15 11:38       ` Anthony G. Basile
2015-10-15 11:47         ` Jason Zaman
2015-10-15 11:58           ` Alexander Tsoy
2015-10-15 12:02             ` Alexander Tsoy
2015-10-15 12:36             ` Rich Freeman
2015-10-15 15:11               ` [gentoo-dev] " Duncan
2015-10-16  7:14                 ` netfab
2015-10-16 23:42                   ` Anthony G. Basile
2015-10-16 23:49                     ` Peter Stuge
2015-10-17  0:03                       ` Anthony G. Basile
2015-10-17  0:15                         ` Peter Stuge
2015-10-15 18:50               ` [gentoo-dev] " Mike Gilbert
2015-10-15 11:35   ` Anthony G. Basile
2015-10-15 11:30 ` Anthony G. Basile

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='pan$4526d$f94981d4$9f9a22cc$1e2e87bb@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox