From: "Michael Kerrisk" <mtk-manpages@gmx.net>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: linux-kernel@vger.kernel.org
Subject: signalfd() semantics after execve()
Date: Sat, 14 Jul 2007 09:41:45 +0200 [thread overview]
Message-ID: <20070714074145.277260@gmx.net> (raw)
Davide,
I'm working on the signalfd(2) man page, and I've come
acorss some puzzling behaviour...
What are the intended semantics of a signalfd file descriptor
after an execve()?
As far as I can work out, after an execve() the file descriptor
is still available, but reads from it always return 0, even if:
a) there were signals pending before the execve().
However, sigpending() shows the signal as pending,
and the signal can be accepted using sigwaitinfo().
b) we generate a signal after the execve().
Is this intended behavior (the "orphaned sighand" condition
mentioned in the draft man page you sent me?)? Is it a bug?
Cheers,
Michael
--
Michael Kerrisk
maintainer of Linux man pages Sections 2, 3, 4, 5, and 7
Want to help with man page maintenance?
Grab the latest tarball at
http://www.kernel.org/pub/linux/docs/manpages ,
read the HOWTOHELP file and grep the source
files for 'FIXME'.
next reply other threads:[~2007-07-14 7:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-14 7:41 Michael Kerrisk [this message]
2007-07-14 18:53 ` signalfd() semantics after execve() Davide Libenzi
2007-07-15 9:17 ` Michael Kerrisk
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=20070714074145.277260@gmx.net \
--to=mtk-manpages@gmx.net \
--cc=davidel@xmailserver.org \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.