Created attachment 4230 [details] log I'm reliably seeing a large number of host-user-contaminated warnings with poky, mostly against glibc, coreutils, and ncurses, on Fedora 27. Attached is the log of a fresh clone of poky followed by a core-image-minimal build, where I get a couple hundred lines of warnings. This also occurs with the HEAD and yocto-2.4.1 tag of rocko, so its not recent. I didn't see this immediately upon upgrade to Fedora 27. I think it started happening when I wiped out my sstate cache. This could be related to bug 12434.
I was able to reproduce the problem on my Fedora 27 system as well. Nothing jumped out of the logs so it's likely a pseudo regression.
Can you replicate with rocko branch so we can determine if its a F27 change, or the pseudo upgrade? CCing Seebs.
Huh, interesting! Would like to see a small reproducer. The main place I'd be looking for things would be the general vicinity of the O_TMPFILE changes, but I didn't think that was heavily used. Unless it's related to the mk*temp() functions, but again, thought those were lightly used.
A quick reproducer for me: bitbake gawk -c cleanall; bitbake gawk
-ccleanall is an antipattern, to force a rebuild use bitbake -C unpack gawk.
It happens on rocko HEAD and several other commits before that. Can't bisect because of a build failure. I'm guessing it's host-user-contaminated all the way down.
My hunch is that glibc 2.27 is using some functions which pseudo isn't intercepting?
That seems pretty likely. I don't have a Fedora 27 box handy, though.
| $ ltrace mv foo bar | ... | syscall(316, 0xffffff9c, 0x7fff1564a341, 0xffffff9c) = 0 Yeah, that would do it. Any F27 machine with https://src.fedoraproject.org/rpms/coreutils/c/79fe59c7fc11afa211a15bfcf28f4ca76f42c645?branch=master will be hitting this.
http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=5b68f72e590546958a742f64f3501f1abaa22267