From: Roland McGrath <roland@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: mtk.manpages@gmail.com, LKML <linux-kernel@vger.kernel.org>,
Oleg Nesterov <oleg@tv-sign.ru>, Ingo Molnar <mingo@elte.hu>,
Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>,
Linux API <linux-api@vger.kernel.org>
Subject: Re: [patch 0/3] add rt_tgsigqueueinfo syscall [RESEND]
Date: Mon, 23 Mar 2009 23:58:58 -0700 (PDT) [thread overview]
Message-ID: <20090324065858.153BAFC3AB@magilla.sf.frob.com> (raw)
In-Reply-To: Thomas Gleixner's message of Monday, 23 March 2009 12:14:59 +0100 <alpine.LFD.2.00.0903231213180.29264@localhost.localdomain>
> > I don't see any rationale for rt_tgsigqueueinfo and rt_sigqueueinfo to
> > differ in their treatment of si_pid/si_uid (whatever that is). It just
> > seems like common sense that they would match.
> >
> > Oleg and/or Sukadev have some patches floating around (maybe all in -mm?)
> > that relate to setting those.
>
> You mean having the same logic as we have in {t,tg,}kill syscalls for
> rt_sigqueueinfo as well ?
I mean just what I said: rt_tgsigqueueinfo's treatment of the siginfo_t
should match rt_sigqueueinfo's. Make it match rt_sigqueueinfo today and
make sure that if rt_sigqueueinfo changes, then rt_tgsigqueueinfo will
change to match.
> Is there anything else which stands in the way of getting the
> rt_tgsigqueueinfo interface merged ?
I don't see any problem. But you should at least make sure that Ulrich
likes the syscall interface for implementing pthread_sigqueue or whatever
it will be.
Thanks,
Roland
prev parent reply other threads:[~2009-03-24 6:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-26 13:35 Thomas Gleixner
2009-02-26 13:35 ` [patch 1/3] signals: split do_tkill Thomas Gleixner
2009-02-26 13:35 ` [patch 2/3] signals: implement sys_rt_tgsigqueueinfo Thomas Gleixner
2009-02-26 13:35 ` [patch 3/3] x86: hookup sys_rt_tgsigqueueinfo Thomas Gleixner
2009-02-26 21:19 ` [patch 0/3] add rt_tgsigqueueinfo syscall [RESEND] Michael Kerrisk
2009-02-26 22:13 ` Thomas Gleixner
2009-02-28 1:53 ` Michael Kerrisk
2009-02-28 2:44 ` Roland McGrath
2009-02-28 8:46 ` Michael Kerrisk
2009-02-27 0:03 ` Roland McGrath
2009-03-23 11:14 ` Thomas Gleixner
2009-03-24 6:58 ` Roland McGrath [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=20090324065858.153BAFC3AB@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mtk.manpages@gmail.com \
--cc=oleg@tv-sign.ru \
--cc=sukadev@linux.vnet.ibm.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
Powered by JetHome