Re: pseudo: host user contamination

[Enrico Scholz <enrico.scholz@sigma-chemnitz.de>]

"Burton, Ross" <ross.burton@intel.com> writes:

>> do_install() {
>>         install -D -p -m 0644 bar ${D}/bin/bar
>>         install -d -m 0755 ${D}/usr/bin
>>         mv ${D}/bin/bar ${D}/usr/bin/bar
>>         ln -s /usr/bin/bar ${D}/bin/bar
>> }
>>
>> FILES_${PN} = "/bin/* /usr/bin/*"
>> ---
>>
>> WARNING: foo-1.0-r0 do_package_qa: QA Issue: foo: /foo/usr/bin/bar
>> is owned by uid 505, which is the same as the user running
>> bitbake. This may be due to host contamination
>> [host-user-contaminated]
>
> Works for me: install correctly changes owner to root:root as it
> should.

I think, 'mv' is the culprit.  It calls 'renameat2()' directly over
'syscall()':

| $ ltrace mv foo bar
| ...
| syscall(316, 0xffffff9c, 0x7fff1564a341, 0xffffff9c)                                            = 0


Perhaps, 'pseudo' does not catch this?


Enrico