pseudo gets confused by tar and aborts

pseudo gets confused by tar and aborts

[Andrej Shadura]

Hi,

Helmut Grohne reported a bug in pseudo, which, upon further 
investigation, happens when tar (at least v1.34) is extracting a file.

My initial reproducer was this:

$ cd /tmp
$ PSEUDO_PREFIX=/usr PSEUDO_LOCALSTATEDIR=/tmp/state pseudo /bin/bash
# mkdir -p foobar
# tar -C /lib -c -f - . | tar -C /tmp/foobar -xv
./
./cryptsetup/
./cryptsetup/cryptdisks-functions
./cryptsetup/functions
./cryptsetup/scripts/
./cryptsetup/scripts/decrypt_ssl
./cryptsetup/scripts/decrypt_keyctl
./cryptsetup/scripts/decrypt_gnupg
./cryptsetup/scripts/decrypt_gnupg-sc
./cryptsetup/scripts/passdev
./cryptsetup/scripts/decrypt_opensc
./cryptsetup/scripts/decrypt_derived
./cryptsetup/askpass
abort()ing pseudo client by server request. See 
https://wiki.yoctoproject.org/wiki/Pseudo_Abort for more details on this.
Check logfile: /tmp/state/pseudo.log
Aborted
# cat /tmp/state/pseudo.log
debug_logfile: fd 2
pid 977255 [parent 977254], doing new pid setup and server start
Setup complete, sending SIGUSR1 to pid 977254.
path mismatch [2 links]: ino 18745211 db 
'/tmp/foobar/cryptsetup/scripts' req '/proc/self/fd/4'.
#

However, the same happened when I pre-tarred /lib and extracted it:

# tar -C /lib -c -f /tmp/test.tar .
# tar -C /tmp/foobar -xv -f /tmp/test.tar
./
./cryptsetup/
./cryptsetup/cryptdisks-functions
./cryptsetup/functions
./cryptsetup/scripts/
./cryptsetup/scripts/decrypt_ssl
./cryptsetup/scripts/decrypt_keyctl
./cryptsetup/scripts/decrypt_gnupg
./cryptsetup/scripts/decrypt_gnupg-sc
./cryptsetup/scripts/passdev
./cryptsetup/scripts/decrypt_opensc
./cryptsetup/scripts/decrypt_derived
./cryptsetup/askpass
./cryptsetup/checks/
./cryptsetup/checks/ext2
./cryptsetup/checks/un_blkid
./cryptsetup/checks/swap
./cryptsetup/checks/blkid
./cryptsetup/checks/xfs
./linux-sound-base/
abort()ing pseudo client by server request. See 
https://wiki.yoctoproject.org/wiki/Pseudo_Abort for more details on this.
Check logfile: /tmp/state/pseudo.log
Aborted


-- 
Cheers,
   Andrej

Re: pseudo gets confused by tar and aborts

[Andrej Shadura]

On 17/01/2022 21:25, Andrej Shadura wrote:
> Hi,
> 
> Helmut Grohne reported a bug in pseudo, which, upon further 
> investigation, happens when tar (at least v1.34) is extracting a file.
...
> # tar -C /lib -c -f /tmp/test.tar .
> # tar -C /tmp/foobar -xv -f /tmp/test.tar
> ./
...
> ./linux-sound-base/
> abort()ing pseudo client by server request. See 
> https://wiki.yoctoproject.org/wiki/Pseudo_Abort for more details on this.
> Check logfile: /tmp/state/pseudo.log

A bit more with extra verbosity:

chown /tmp/foobar/udev/hwdb.d [18745405]: incoming: 
'/tmp/foobar/udev/hwdb.d'+ [18745405]+
owner 0:0 completed chown.
open /tmp/foobar/udev/hwdb.d [18745405]: incoming: 
'/tmp/foobar/udev/hwdb.d'+ [18745405]+
completed open.
stat /tmp/foobar/udev/hwdb.d [18745405]: incoming: 
'/tmp/foobar/udev/hwdb.d'+ [18745405]+
stat, ino 18745405 (old mode 040700): mode 040700
completed stat.
chmod /proc/self/fd/5 [18745405]: incoming: '/proc/self/fd/5'- [18745405]+
path mismatch [2 links]: ino 18745405 db '/tmp/foobar/udev/hwdb.d' req 
'/proc/self/fd/5'.
completed chmod.

I understand this is related to the latest commit to pseudo:
https://git.yoctoproject.org/pseudo/commit/?h=oe-core&id=300d7570720bc1

-- 
Cheers,
   Andrej