Le 06/04/2026 à 20:13, Rainer Weikusat via Dng a écrit :
> This cannot possibly work in this way because otherwise, signals might
> be received twice. And it obviously doesn't work in this way. The
> signalfd read function just calls dequeue_signal, like anything else
> which wants to receive signals.

    You're right, the kernel implementation calls dequeue_signal() just
when the application reads from the file descriptor, which means
signalfd() is just a file-style API, but not a queue where the signals
would be stored. Too bad! It is nevertheless convenient to serialize the
signals, process them in the normal context of the application instead
of a signal handler, and wait for them at the same wait point as
possible other asynchronous events.

--     Didier