Rich Freeman posted on Thu, 15 Oct 2015 08:36:59 -0400 as excerpted: > On Thu, Oct 15, 2015 at 7:58 AM, Alexander Tsoy <[email protected]> > wrote: >> >> I was wrong. This patch was not merged upstream. It is still needed and >> included in latest genpatches for 4.2: >> >> $ tar tf genpatches-4.2-6.base.tar.xz | grep XATTR >> ./1500_XATTR_USER_PREFIX.patch > > I suspect what we all have in common then is that we're using tmpfs to > do builds and we're not using genpatches. > > If the warning isn't an issue for non-hardened users then I don't see > any need to change anything. Is the patch (or something similar) > likely to get merged? It doesn't really seem ideal to be dependent on > something not in mainline.
Having just completed an update and checked the warnings, which occurred on firefox and llvm, I can confirm that the paths mentioned in the warnings are in the tmpfs PORTAGE_TMPDIR, *not* on btrfs. And I run a mainline (direct git, in fact) kernel. So the problem does indeed appear to be PORTAGE_TMPDIR on tmpfs, on a kernel without the gentoo patches. AFAIK pax markings only matter if pax is enabled, which it won't be on mainline kernels since I don't believe they include the pax patches. So the warnings, while annoying, don't signify a real problem. But it would definitely be nice to have them turned off, or even have the entire attempt to do pax markings in the first place turned off, on non- hardened kernels. In any case, doesn't seem to be btrfs related at all. False alarm there. =:^) -- 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
