8f00bdb4a6
In case of remote process exit even when some messages are still waiting, vchan connection can be already closed. If we try to send some data in this case (for example stdout of local process), there will be an error, which will terminate qrexec-client-vm/qrexec-agent child. So first check vchan data (where could be MSG_EXIT_CODE queued) , then local process. There is still some race condition in this code - remote process could exit just after we check vchan, but before we send some data. But this is much less probable and in the worst case we only loose remote process exit code. |
||
---|---|---|
archlinux | ||
debian | ||
doc | ||
misc | ||
network | ||
pkgs | ||
qrexec | ||
qubes-rpc | ||
rpm_spec | ||
vm-init.d | ||
vm-systemd | ||
.gitignore | ||
debian-quilt | ||
LICENSE | ||
Makefile | ||
Makefile.builder | ||
series-debian-vm.conf | ||
version |