From: Andrew Clayton <andrew@digital-domain.net>
To: mtk.manpages@gmail.com
Cc: linux-man@vger.kernel.org, Andrew Clayton <andrew@digital-domain.net>
Subject: [PATCH 0/1] Point out the interactions of signalfd with epoll & fork
Date: Sat, 21 Sep 2019 00:42:10 +0100 [thread overview]
Message-ID: <20190920234211.57596-1-andrew@digital-domain.net> (raw)
Hi Michael,
I was just hit by this interaction of signalfd with epoll & fork.
Basically if you add a signalfd file descriptor to epoll and then fork,
you won't receive notifications for sent signals,
Hopefully this addition to the man page will help avoid people head
scratching in the future.
I've added links and quotes to the sources for this problem in the
commit message.
Hopefully the text is OK. I don't really understand what is going on
underneath.
Cheers,
Andrew
Andrew Clayton (1):
signalfd.2: Note about interactions with epoll & fork
man2/signalfd.2 | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
--
2.21.0
next reply other threads:[~2019-09-21 0:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 23:42 Andrew Clayton [this message]
2019-09-20 23:42 ` [PATCH 1/1] signalfd.2: Note about interactions with epoll & fork Andrew Clayton
2019-09-23 14:49 ` Michael Kerrisk (man-pages)
2019-09-23 21:24 ` Andrew Clayton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190920234211.57596-1-andrew@digital-domain.net \
--to=andrew@digital-domain.net \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).