From: "Ulrich Drepper" <drepper@gmail.com>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: "Davide Libenzi" <davidel@xmailserver.org>,
"Jeremy Fitzhardinge" <jeremy@goop.org>,
"Stephen Rothwell" <sfr@canb.auug.org.au>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>
Subject: Re: [patch 1/4] signalfd v1 - signalfd core ...
Date: Wed, 7 Mar 2007 14:01:33 -0800 [thread overview]
Message-ID: <a36005b50703071401m2b166832rb06f4cf73224f45e@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0703071347380.5963@woody.linux-foundation.org>
On 3/7/07, Linus Torvalds <torvalds@linux-foundation.org> wrote:
> > 1) You want standard delivery only:
> >
> > - Just dont use signalfd
> >
> > 2) you want signalfd only:
> >
> > - Do a sigprocmask(SIG_BLOCK) of the same mask you pass to signalfd
> >
> > If you want both, you can have it. Race free.
>
> .. but maybe with more code and lots of confusion. I'm still unclear on
> any upsides here.
>
> Choice is good, but only if it's *useful* choice.
Not only that. If you don't force that the signal is blocked when
using signalfd() you are bound to run into problems. For the same
reason is it required to have signals blocked when you use sigwait()
etc. Don't try to innovate here, I guarantee you it's going to break
something somewhere.
next prev parent reply other threads:[~2007-03-07 22:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-07 1:36 Davide Libenzi
2007-03-07 1:43 ` Davide Libenzi
2007-03-07 4:55 ` Stephen Rothwell
2007-03-07 7:11 ` Davide Libenzi
2007-03-07 12:38 ` Stephen Rothwell
2007-03-07 16:57 ` Linus Torvalds
2007-03-07 17:50 ` Davide Libenzi
2007-03-07 20:30 ` Jeremy Fitzhardinge
2007-03-07 20:56 ` Davide Libenzi
2007-03-07 21:26 ` Jeremy Fitzhardinge
2007-03-07 21:35 ` Davide Libenzi
2007-03-07 21:48 ` Linus Torvalds
2007-03-07 22:01 ` Ulrich Drepper [this message]
2007-03-07 22:10 ` Davide Libenzi
2007-03-16 5:16 ` Ulrich Drepper
2007-03-16 6:31 ` Davide Libenzi
2007-03-07 22:01 ` Davide Libenzi
2007-03-07 22:14 ` Jeremy Fitzhardinge
2007-03-07 22:21 ` Davide Libenzi
2007-03-07 17:42 ` Davide Libenzi
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=a36005b50703071401m2b166832rb06f4cf73224f45e@mail.gmail.com \
--to=drepper@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=davidel@xmailserver.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®