public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Kerrisk <mtk-manpages@gmx.net>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: signalfd and thread semantics
Date: Tue, 17 Jul 2007 22:44:48 +0200	[thread overview]
Message-ID: <469D2A40.2060008@gmx.net> (raw)

Hi Davide,

Working on the signalfd man page, another question comes up:

What are the intended semantics for a signalfd file descriptor with respect
to threads?  I have not yet tested the behavior, but in any case, I better
check what is expected.

A signal can be directed to the process as a whole (e.g., using kill(2)),
or to a particular thread (using, e.g., pthread_kill(2), or tgkill(2)).

So that raises the question: If a thread calls signalfd(), does the
resulting file descriptor return just those signals directed to [the thread
and the process as a whole], or will it also receive signals that are
targeted at other threads in the process?  I would hope the former is the
case, but I'm not sure what has been implemented (or intended).

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'.


             reply	other threads:[~2007-07-17 21:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-17 20:44 Michael Kerrisk [this message]
2007-07-17 22:33 ` signalfd and thread semantics Davide Libenzi
2007-07-17 22:40   ` 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=469D2A40.2060008@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox