Control: reopen -1 Control: retitle -1 /proc/self/exe under qemu-user points to qemu binary not to the binary being run Control: tag -1 + confirmed
03.11.2020 12:05, L3P3 wrote: []
code, like all electron (chromium) apps, calls /proc/self/exec to start its integrated gpu process. The other subprocesses like zygote get called by the actual path of the electron binary. In qemu, for some weird reason, this link points to the qemu binary instead of the target binary.
Hmm. I just closed this bugreport but apparently I forgot about this piece of information, and this piece makes the bug to be different from another related bug I actually closed. So I'm reopening it now. And retitling, as its current title is too similar to that other bug..
There are actually some other target apps that fail due to that violation.
There should be, indeed.
A workaround would be to just not use /proc/self/exec but in my opinion it is a qemu-user bug since it is violating the principle of transparency.
Well, /proc/self/exe is maintained by the kernel, not qemu. It is just like a shell script, the actual executable /proc/self/exe points to is the shell, not the script. Qemu-user can catch reading of /proc/self/exe but this is not a simple question, - where should we draw a line, should we catch every system call like this? And it definitely should not be answered in debian. Thanks, /mjt
