From: Davide Libenzi <davidel@xmailserver.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [patch 1/4] signalfd v1 - signalfd core ...
Date: Tue, 6 Mar 2007 23:11:49 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0703062301590.10398@alien.or.mcafeemobile.com> (raw)
In-Reply-To: <20070307155553.06c82ca1.sfr@canb.auug.org.au>
On Wed, 7 Mar 2007, Stephen Rothwell wrote:
> On Tue, 6 Mar 2007 17:36:56 -0800 (PST) Davide Libenzi <davidel@xmailserver.org> wrote:
> >
> > The read(2) call will read u32 signal numbers that landed over the
> > signalfd. It returns the size of the data copied, or zero if the sighand
> > we are attached to, has been detached.
>
> So what about signals that the user asked for a siginfo_t to be returned
> with?
O-Ren: "You didn't think it was gonna be that easy, did you?"
B-Kiddo: "You know, for a second there, yeah, I kinda did."
:)
I could do that, since where I placed the signalfd_notify() I have the
siginfo. But that is going to make code a little more complex, since the
simple bitmaks needs to become a queue.
- Davide
next prev parent reply other threads:[~2007-03-07 7:13 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 [this message]
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
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=Pine.LNX.4.64.0703062301590.10398@alien.or.mcafeemobile.com \
--to=davidel@xmailserver.org \
--cc=akpm@linux-foundation.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®