All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Rohland <cr@sap.com>
To: Paul Menage <pmenage@ensim.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH][RFC] Pollable /proc/<pid>/ - avoid SIGCHLD/poll() races
Date: 04 Oct 2001 12:25:36 +0200	[thread overview]
Message-ID: <m3snczogal.fsf@linux.local> (raw)
In-Reply-To: <E15p4qy-0000yf-00@pmenage-dt.ensim.com>
In-Reply-To: <E15p4qy-0000yf-00@pmenage-dt.ensim.com>

Hi Paul,

On Thu, 04 Oct 2001, Paul Menage wrote:
>>> The only real user-space solution to this is to have the SIGCHLD
>>> handler somehow cause the select() to return immediately
>>
>>... or implement pselect:
>>http://mesh.eecs.umich.edu/cgi-bin/man2html/usr/share/man/man2/select.2.gz
> 
> Agreed, althought that's not a user-space solution. Is there any
> fundamental reason why no-one's implemented pselect()/ppoll() for
> Linux yet?

Missing knowledge and/or demand? It should be pretty easy to
implement.

>>or use sigsetjmp/siglongjmp
> 
> Yes, that would probably solve the situation in question, provided
> that siglongjmp() is portably safe. (A comment on LKML in the past
> suggested that it's not safe on cygwin, for example.)

It should be at least portable between different U*X versions. I never
used cygwin though.

Greetings
		Christoph



  reply	other threads:[~2001-10-04 10:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-04  7:52 [PATCH][RFC] Pollable /proc/<pid>/ - avoid SIGCHLD/poll() races Paul Menage
2001-10-04  8:59 ` Christoph Rohland
2001-10-04  9:31   ` Paul Menage
2001-10-04 10:25     ` Christoph Rohland [this message]
2001-10-13 15:44     ` Jamie Lokier
2001-10-04 14:18 ` Mattias Engdegård
2001-10-04 20:39   ` Paul Menage
2001-10-05  9:36     ` Mattias Engdegård
2001-10-13 15:36   ` Jamie Lokier
2001-10-14  2:25     ` John Alvord

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=m3snczogal.fsf@linux.local \
    --to=cr@sap.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmenage@ensim.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 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.