From: Michael Kerrisk <mtk.manpages@googlemail.com>
To: Roland McGrath <roland@redhat.com>
Cc: Oleg Nesterov <oleg@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
Ulrich Drepper <drepper@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [patch 0/3] add rt_tgsigqueueinfo syscall -V2
Date: Wed, 1 Apr 2009 14:44:26 +1300 [thread overview]
Message-ID: <cfd18e0f0903311844nd5ab221g6bff6cf5fc73de42@mail.gmail.com> (raw)
In-Reply-To: <20090401012547.3B581FC3AB@magilla.sf.frob.com>
On Wed, Apr 1, 2009 at 2:25 PM, Roland McGrath <roland@redhat.com> wrote:
>> 1) With rt_siqueueinfo(), we can get the PID (TGID) of the sender,
>
> No. You can get whatever the caller put into the siginfo_t.
> Only the si_signo field is set by the kernel.
>
>> With rt_tgsigqueueinfo(), [...]
>
> You still get whatever the caller put into the siginfo_t.
Yes. I wrote the text awkwardly, but I think the point was clear. In
my point 1, I wrongly thought we needed a way to get the sender's TID
to the receiver, and you pointed out that sigval could do the job. In
my point 2, I made the same observation as you just made above.
Thanks,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
git://git.kernel.org/pub/scm/docs/man-pages/man-pages.git
man-pages online: http://www.kernel.org/doc/man-pages/online_pages.html
Found a bug? http://www.kernel.org/doc/man-pages/reporting_bugs.html
prev parent reply other threads:[~2009-04-01 1:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 10:35 Thomas Gleixner
2009-03-24 10:35 ` [patch 1/3] signals: split do_tkill Thomas Gleixner
2009-03-24 10:35 ` [patch 2/3] signals: implement sys_rt_tgsigqueueinfo Thomas Gleixner
2009-03-24 10:35 ` [patch 3/3] x86: hookup sys_rt_tgsigqueueinfo Thomas Gleixner
2009-03-31 15:26 ` [patch 0/3] add rt_tgsigqueueinfo syscall -V2 Oleg Nesterov
2009-04-01 1:16 ` Michael Kerrisk
2009-04-01 1:25 ` Roland McGrath
2009-04-01 1:44 ` Michael Kerrisk [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=cfd18e0f0903311844nd5ab221g6bff6cf5fc73de42@mail.gmail.com \
--to=mtk.manpages@googlemail.com \
--cc=akpm@linux-foundation.org \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mtk.manpages@gmail.com \
--cc=oleg@redhat.com \
--cc=roland@redhat.com \
--cc=tglx@linutronix.de \
/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®