[OE-core] pseudo: host user contamination

Burton, Ross ross.burton at intel.com
Fri Mar 23 16:06:28 UTC 2018


Ah, I just read this other message of yours, which includes the fact
that you're on F27.

Yes, something in F27 has just broken pseudo quite dramatically.  No
idea what, so far.

Ross

On 23 March 2018 at 15:33, Enrico Scholz
<enrico.scholz at sigma-chemnitz.de> wrote:
> Hello,
>
> in some packages (e.g. ncurses or glibc) I get package-qa warnings due
> to host user contamination; e.g.
>
> | WARNING: ncurses-6.0+20170715-r0 do_package_qa: QA Issue: ncurses: /ncurses-terminfo-base/etc/terminfo/a/ansi is owned by uid 505, which is the same as the user running bitbake. This may be due to host contamination
> | ncurses: /ncurses-terminfo-base/etc/terminfo/d/dumb is owned by uid 505, which is the same as the user running bitbake. This may be due to host contamination
> | ...
> | ncurses: /ncurses-terminfo-base/etc/terminfo/x/xterm-256color is owned by uid 505, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
>
>
> This is 100% reproducible by 'bitbake ncurses -c cleansstate && bitbake
> ncurses'.
>
>
> Pseudo log contains
>
> | debug_logfile: fd 2
> | pid 16096 [parent 16095], doing new pid setup and server start
> | Setup complete, sending SIGUSR1 to pid 16095.
> | path mismatch [2 links]: ino 382716451 db '/dev/shm/sem.mp-6eoy3v9n' req '/dev/shm/8JXYzj'.
> | inode mismatch: '..../ncurses/6.0+20170715-r0/image/usr/share/terminfo/a/ansi' ino 39261519 in db, 39262517 in request.
> | symlink mismatch: '..../ncurses/6.0+20170715-r0/image/usr/share/terminfo/a/ansi' [39261519] db mode 0100644, header mode 0120777 (unlinking db)
>
> for all the reported files.and a lot of
>
> | path mismatch [91 links]: ino 1605070 db ...
>
> like messages for unrelated files (e.g  sysroot components).
>
>
> Seen on recent rocko and master (1-2 weeks before).
>
> System is Fedora 27 in a docker container; rootfs is on an overlaysfs,
> recipes on a bind-mounted btrfs fs and build (TMPDIR) happens in an ext4
> fs.  SELinux is active.
>
>
>
> Is this issue known resp. does a solution exist?
>
>
>
> Enrico
> --
> SIGMA Chemnitz GmbH       Registergericht:   Amtsgericht Chemnitz HRB 1750
> Am Erlenwald 13           Geschaeftsfuehrer: Grit Freitag, Frank Pyritz
> 09128 Chemnitz
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core



More information about the Openembedded-core mailing list