From: "Michael Kerrisk" <michael.kerrisk@gmx.net>
To: David Woodhouse <dwmw2@infradead.org>
Cc: drepper@redhat.com, jakub@redhat.com, torvalds@osdl.org,
linux-kernel@vger.kernel.org, akpm@osdl.org,
michael.kerrisk@gmx.net, mtk-lkml@gmx.net
Subject: Re: Add pselect, ppoll system calls.
Date: Fri, 26 Aug 2005 08:46:29 +0200 [thread overview]
Message-ID: <430ED6E5.29250.328C39C@localhost> (raw)
In-Reply-To: <1124928289.7316.92.camel@baythorne.infradead.org>
David,
> On Fri, 2005-08-05 at 14:49 +0200, Michael Kerrisk wrote:
> > If I change your program to do something like the above, I also
> > do not see a message from the handler -- i.e., it is not being
> > called, and I'm pretty sure it should be.
>
> Hm, yes. What happens is we come back out of the select() immediately
> because of the pending signal, but on the way back to userspace we put the
> old signal mask back... so by the time we check for it, there _is_ no
> (unblocked) signal pending.
>
> If it's mandatory that we actually call the signal handler,
I'm just about to go off on holiday, and don't have a chance to pull up
all the relevant standards details at them moment. However, I'm fairly
sure that the signal handler should be called. (Try running a modified
version of my program on Solaris 10 or the Unix-03 conversion of AIX
(5.3?).)
> then we need to
> play tricks like sigsuspend() does to leave the old signal mask on the
> stack frame. That's a bit painful atm because do_signal is different
> between architectures.
Yes, I'd say the behaviour should in fact be like what sigsuspend() does.
Cheers,
Michael
next prev parent reply other threads:[~2005-08-26 6:47 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-10 22:58 Add pselect, ppoll system calls David Woodhouse
2005-06-12 22:48 ` Alan Cox
2005-06-13 0:26 ` Linus Torvalds
2005-06-13 1:16 ` jnf
2005-06-13 3:26 ` Linus Torvalds
2005-06-13 6:22 ` Ulrich Drepper
2005-06-13 9:16 ` bert hubert
2005-06-13 9:41 ` David Woodhouse
2005-06-13 11:05 ` Christoph Hellwig
2005-06-13 11:14 ` Jakub Jelinek
2005-06-13 11:24 ` David Woodhouse
2005-06-13 15:38 ` Ulrich Drepper
2005-06-13 16:02 ` David Woodhouse
2005-06-13 16:10 ` Ulrich Drepper
2005-06-13 16:29 ` David Woodhouse
2005-06-13 16:31 ` Ulrich Drepper
2005-06-13 21:58 ` David Woodhouse
2005-06-13 22:01 ` Ulrich Drepper
2005-06-13 16:36 ` Jakub Jelinek
2005-06-15 11:36 ` David Woodhouse
2005-08-05 10:42 ` pselect() modifying timeout Michael Kerrisk
2005-08-05 14:50 ` Ulrich Drepper
2005-08-05 20:08 ` Michael Kerrisk
2005-08-08 11:10 ` Alan Cox
2005-08-05 11:58 ` Add pselect, ppoll system calls Michael Kerrisk
2005-08-05 12:49 ` Michael Kerrisk
2005-08-25 0:04 ` David Woodhouse
2005-08-25 0:34 ` Ulrich Drepper
2005-08-26 6:46 ` Michael Kerrisk [this message]
2005-06-13 15:35 ` Ulrich Drepper
2005-06-13 7:23 ` Benjamin Herrenschmidt
2005-06-13 7:29 ` David Woodhouse
2005-06-13 22:56 ` Benjamin Herrenschmidt
2005-06-13 11:15 ` Alan Cox
2005-06-13 11:27 ` David Woodhouse
2005-06-13 15:40 ` Ulrich Drepper
-- strict thread matches above, loose matches on Subject: below --
2005-06-13 19:38 Mattias Engdegård
2005-06-13 19:57 ` Chris Friesen
2005-06-13 20:08 ` Mattias Engdegård
2005-06-13 20:23 ` Valdis.Kletnieks
2005-06-14 14:07 ` Mattias Engdegård
2005-06-14 14:16 ` Bernd Petrovitsch
2005-06-14 14:42 ` Mattias Engdegård
2005-06-14 14:54 ` Bernd Petrovitsch
2005-06-14 15:27 ` Valdis.Kletnieks
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=430ED6E5.29250.328C39C@localhost \
--to=michael.kerrisk@gmx.net \
--cc=akpm@osdl.org \
--cc=drepper@redhat.com \
--cc=dwmw2@infradead.org \
--cc=jakub@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk-lkml@gmx.net \
--cc=torvalds@osdl.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.