Re: [PULL 02/15] linux-user: Move syscall error detection into safe_syscall_base

[Richard Henderson]

On 1/4/22 5:51 AM, Laurent Vivier wrote:
> This patch breaks command execution in bash command line interface:
>
> - if I run "chroot chroot/powerpc/jessie ls", it works
>
> - if I run "echo ls |  chroot chroot/powerpc/jessie", it hangs
>
> - if I run "chroot chroot/powerpc/jessie bash invalid_command",
>    it does nothing whereas it should return "bash: invalid_command: No such file or 
> directory".

Thanks.  I've reproduced this (or something close enough):

Host:
openat(AT_FDCWD, "asdf", O_RDONLY) = -1 ENOENT (No such file or directory)

Guest:
502138 open("asdf",O_RDONLY|O_LARGEFILE) = 100


r~