On Mon, Sep 11, 2023 at 11:14:31AM +0100, Phillip Wood wrote:
On 11/09/2023 11:00, Phillip Wood wrote:
There is an inevitable race between wait() returning and calling
signal() to restore the handlers for SIGINT and SIGQUIT,
In principle if we installed a signal handler to set a flag if a signal
is received while calling wait() and then once wait() returns
successfully see if the child was killed we can tell if the signal was
received while the child was alive.
yes, this is what i was already writing:
my point is that you shouldn't be doing that in the first place.
install the handlers when the sequencer is entered and leave them there.
the handlers need to set (volatile) flag variables, which are checked by
the sequencer on a regular basis.
a few notes on that:
- install without SA_RESTART, so syscalls can actually return with EINTR
and give us the opportunity to check the flag.
- an alternative to setting flags is setjmp()/longjmp(), but you really
don't want to go there.
- install with SA_RESETHAND, so the second ctrl-c will kill git
regardless, providing an escape hatch.
In practice if the child is catching SIGINT or SIGQUIT we cannot rely
on it re-raising the signal so that wont work.
yes, but that's a minor issue, i think.
by far most hooks and other things that might be invoked within
sequencer context don't mess with signals in the first place.
the things that do should be presumed to do the right thing, which means
at least a non-zero exit status in case of a premature termination,
which will yield pretty much the same effect on our side anyway.
so the only actually problematic situation would be us completely
ignoring the exit code (like the git-gc call, but that's clearly a bug
in git, and we control both sides, so it's easily fixable).
regards
