mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Davide Libenzi <davidel@xmailserver.org>
To: Michael Kerrisk <mtk.manpages@googlemail.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: signalfd() not handling sigqueue() sigval data correctly
Date: Thu, 10 Apr 2008 10:21:54 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0804101019270.9405@alien.or.mcafeemobile.com> (raw)
In-Reply-To: <cfd18e0f0804100332v5d5d9becqbd0a612ca81abfe8@mail.gmail.com>

On Thu, 10 Apr 2008, Michael Kerrisk wrote:

> On Thu, Apr 10, 2008 at 7:03 AM, Michael Kerrisk
> <mtk.manpages@googlemail.com> wrote:
> > Hi Davide,
> >
> > > > I was doing some playing about with signalfd(), and seem to have encountered a
> > > > bug: when a signalfd read() fetches data for a signal that was sent by
> > > > sigqueue(), the data accompanying the signal is not returned.  Instead
> > > > ssi_int/ssi_ptr is zero.
> > >
> > > Michael, can you give the patch below a spin? I tested it on my x86_64 box
> > > and seems to be working fine:
> > >
> > > Got signal 44
> > >   ssi_code= -1
> > >   ssi_pid = 6314
> > >   ssi_uid = 1000
> > >   ssi_int = 123
> > >   ssi_ptr = 7b
> >
> > This works for me on x86-32.  Thanks Davide!
> 
> Davide,
> 
> Are you going to get this pushed into 2.6.26?  I assume we can't get
> it into 2.6.25...

I'll be sending it Andrew-bound today. I dunno where it'll land mainline.


- Davide



      reply	other threads:[~2008-04-10 17:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-08 21:09 Michael Kerrisk
2008-04-08 23:37 ` Davide Libenzi
2008-04-09  6:31   ` Michael Kerrisk
2008-04-09  7:06     ` Davide Libenzi
2008-04-09 19:59 ` Davide Libenzi
2008-04-10  5:03   ` Michael Kerrisk
2008-04-10 10:32     ` Michael Kerrisk
2008-04-10 17:21       ` Davide Libenzi [this message]

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.0804101019270.9405@alien.or.mcafeemobile.com \
    --to=davidel@xmailserver.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtk.manpages@googlemail.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 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®