All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Pilcher <arequipeno-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: ppoll with multiple threads
Date: Thu, 26 Sep 2013 17:04:46 -0500	[thread overview]
Message-ID: <5244AF7E.1020500@gmail.com> (raw)

The select(2) man page was updated about a year ago to clarify the
behavior of pselect in multi-threaded programs.

http://git.kernel.org/cgit/docs/man-pages/man-pages.git/commit/man2/select.2?id=2e72e991695f745d6419feeb77598f61d8c86a52

Should a similar update be made to poll(2) for ppoll?

If I'm reading the kernel source (fs/select.c) correctly, both syscalls
(pselect6 and ppoll) use a (possibly unfortunately named) "sigprocmask"
function to manipulate the signal mask, so their behavior should be the
same in this regard.

Also, it might be nice to clarify that these changes are clarifications
of existing behavior, rather than new behavior (i.e. clarify the
clarification).  The current situation is pretty confusing:

http://stackoverflow.com/questions/17011460/ppoll-vs-pselect-with-multiple-threads

-- 
========================================================================
Ian Pilcher                                         arequipeno-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Sometimes there's nothing left to do but crash and burn...or die trying.
========================================================================
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2013-09-26 22:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-26 22:04 Ian Pilcher [this message]
     [not found] ` <5244AF7E.1020500-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-05-02  7:01   ` ppoll with multiple threads Michael Kerrisk (man-pages)

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=5244AF7E.1020500@gmail.com \
    --to=arequipeno-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.