git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] sigchain: recover from concurrent double-pops of the same signal

From
Oswald Buddenhagen <oswald.buddenhagen@gmx.de>
Date
Oct 30, 2026, 08:45 UTC
Message-ID
<auRZNlHezwALJOD5@ugly.lan>
In-Reply-To
<4c2728ca-5511-4c30-a2ef-6c32fe7a3e9e@gmail.com>
On Thu, Oct 29, 2026 at 04:03:18PM +0000, Phillip Wood wrote:
Show 8 quoted lines
>On 29/10/2026 14:15, ian4hu wrote:
>> I left SIGPIPE out precisely to keep the "upstream of a pipe
>> dies of SIGPIPE" behaviour that common-init.c restores.  The set I
>> plan to block is SIGINT, SIGHUP, SIGTERM and SIGQUIT.  If you
>> think SIGPIPE belongs in it too, I will add it.
>
>I think we want to block all signals when we create a thread, so that >all signals are handled by the main (initial) thread.
>
that wording again does not address the fact that sigpipe is different due to being thread-directed [1]. even if the outcome is identical, it needs to be reasoned about separately.
[1] https://stackoverflow.com/questions/21718311/when-multi-thread-program-receive-a-sigpipe-signal-because-send-which-thread-wo
Previous: Phillip WoodNext: Phillip Wood
Message 3 of 4 in “Re: [PATCH] sigchain: recover from concurrent double-pops of the same signal”
  1. ian4huOct 29, 2026
  2. Phillip WoodOct 29, 2026
  3. Oswald BuddenhagenOct 30, 2026
  4. Phillip WoodOct 31, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.