Roland,
On Thu, 26 Feb 2009, Roland McGrath wrote:
> 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 ?
Is there anything else which stands in the way of getting the
rt_tgsigqueueinfo interface merged ?
Thanks,
tglx
> > 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