linux-kernel - Re: [RFC patch 0/3] signals: add rt

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 1 Oct 2008 16:57:58 +0200
From:	"Michael Kerrisk" <mtk.manpages@...glemail.com>
To:	"Thomas Gleixner" <tglx@...utronix.de>
Cc:	LKML <linux-kernel@...r.kernel.org>, "Ingo Molnar" <mingo@...e.hu>,
	"Ulrich Drepper" <drepper@...hat.com>,
	"Roland McGrath" <roland@...hat.com>,
	"Oleg Nesterov" <oleg@...sign.ru>, linux-api@...r.kernel.org
Subject: Re: [RFC patch 0/3] signals: add rt_tgsigqueueinfo syscall V2

[CC+=linux-api@...r.kernel.org]

On Wed, Oct 1, 2008 at 12:01 PM, Thomas Gleixner <tglx@...utronix.de> wrote:
> Changes vs. V1: compat_sys_rt_sigqueueinfo implemented. Thanks Roland !
>
> sys_kill has a counterpart sys_tgkill which allows to send signals to
> a particular thread. sys_rt_sigqueueinfo is lacking such a counterpart.
>
> Aside of the asymetry it is a show stopper for migrating applications
> from other unix-alike RTOSes.
>
> The following patch series implements rt_tgsigqueueinfo and hooks it
> up for x86.

This is an excellent candidate for CCing to the new linux-api@...r
(http://thread.gmane.org/gmane.linux.ltp/5658/), since it is an API
change.

> Find below the raw documentation.

Thanks -- I'll work that up into a man page when this gets closer to release.

Cheers,

Michael

> ----
>
> NAME
>       rt_tgsigqueueinfo - Send signal information to a signal to a thread
>
> SYNOPSIS
>       long sys_rt_tgsigqueueinfo (int tgid, int tid, int sig, siginfo_t *uinfo);
>
> DESCRIPTION
>
>       rt_tgsigqueueinfo sends signal sig information uinfo to the
>       thread with the thread ID tid in the thread group tgid.  (By
>       contrast, rt_sigqueueinfo(2) can only be used to send a signal
>       info to a process (i.e., thread group) as a whole, and the
>       signal will be delivered to an arbitrary thread within that
>       process.)
>
> RETURN VALUE
>
>       rt_tgsigqueueinfo returns 0 on success; otherwise,
>       rt_sigqueueinfo returns one of the errors listed in the
>       "Errors" section.
>
> ERRORS
>       -EFAULT
>              An invalid value for uinfo was specified.
>
>       -EINVAL
>              An invalid TID, TGID or signal was specified.
>
>       -EPERM
>              Permission denied.  For the required permissions,
>              see rt_sigqueueinfo(2).
>
>       -ESRCH
>              No process with the specified thread ID and thread group
>              ID exists.
>
>
>



-- 
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/