This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Hurd".
The branch, master has been updated
via 772e292c2d47e9d93455e3c87ae0209a58a3da67 (commit)
from cb372e4d5ae9db30aef20150f1242392459ed808 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 772e292c2d47e9d93455e3c87ae0209a58a3da67
Author: Samuel Thibault <samuel.thiba...@ens-lyon.org>
Date: Tue Aug 23 04:25:54 2022 +0200
Fix spurious EINTR while exec() within fakeroot
The scenario is:
- process running inside fakeroot exec()s
- fakeroot forwards the exec call
- exec starts thrashing the previous process, and notably close its
ports
- the send port that pointed to fakeroot is thus closed
- fakeroot thus receives a no-senders notification
- its libports thus interrupts the current RPC on it, i.e. the exec(),
because it thinks that the caller is no more, but that was exactly the
point of the exec()...
- exec tries to interrupt its own RPCs, at best the execution will fail,
at worse the process is already thrashed and there's nothing better
than burying it for good.
The symptom is processes running inside fakeroot seeming randomly
crashing with SIGKILL.
Making fakeroot keep a send right avoids the no-senders notification,
thus the whole interruption (which was meaningless).
-----------------------------------------------------------------------
Summary of changes:
trans/fakeroot.c | 8 ++++++++
1 file changed, 8 insertions(+)
hooks/post-receive
--
Hurd
