User: Password:
Subscribe / Log in / New account

rt_sigqueueinfo/rt_tgsigqueueinfo man page

From:  Michael Kerrisk <>
To:  Thomas Gleixner <>
Subject:  rt_sigqueueinfo/rt_tgsigqueueinfo man page
Date:  Sun, 18 Sep 2011 17:04:06 +0200
Message-ID:  <>
Cc:  Roland McGrath <>, Oleg Nesterov <>, Michael Kerrisk <mtk.manpages-gM/>, Stephan Mueller <>, linux-man <>, lkml <>, Linux API <>
Archive-link:  Article

Hello Thomas

Long ago (see below) you added the rt_tgsigqueueinfo() syscall, and
provided the essential documentation:

On Thu, Feb 26, 2009 at 2:35 PM, Thomas Gleixner <> wrote:
> 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.
> Find below the raw documentation.
> Thanks,
>        tglx
> ----
>       rt_tgsigqueueinfo - Send signal information to a signal to a thread
>       long sys_rt_tgsigqueueinfo (int tgid, int tid, int sig, siginfo_t *uinfo);
>       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.)
>       rt_tgsigqueueinfo returns 0 on success; otherwise,
>       rt_sigqueueinfo returns one of the errors listed in the
>       "Errors" section.
>       -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.

I've incorporated that documentation into a new rt_sigqueueinfo(2) man
page that documents both rt_sigqueueinfo() and rt_tgsigqueueinfo(). If
you have a moment, could you take a brief look ("man -l <file">) to
see that everything seems sane?



.\" Copyright (c) 2002, 2011 Michael Kerrisk <>
.\" Permission is granted to make and distribute verbatim copies of this
.\" manual provided the copyright notice and this permission notice are
.\" preserved on all copies.
.\" Permission is granted to copy and distribute modified versions of this
.\" manual under the conditions for verbatim copying, provided that the
.\" entire resulting derived work is distributed under the terms of a
.\" permission notice identical to this one.
.\" Since the Linux kernel and libraries are constantly changing, this
.\" manual page may be incorrect or out-of-date.  The author(s) assume no
.\" responsibility for errors or omissions, or for damages resulting from
.\" the use of the information contained herein.  The author(s) may not
.\" have taken the same level of care in the production of this manual,
.\" which is licensed free of charge, as they might when working
.\" professionally.
.\" Formatted or processed versions of this manual, if unaccompanied by
.\" the source, must acknowledge the copyright and authors of this work.
.TH RT_SIGQUEUEINFO 2 2011-09-18 "Linux" "Linux Programmer's Manual"
rt_sigqueueinfo, rt_tgsigqueueinfo \- queue a signal and data
.BI "int rt_sigqueueinfo(pid_t " tgid ", int " sig ", siginfo_t *" uinfo );
.BI "int rt_tgsigqueueinfo(pid_t " tgid ", pid_t " tid ", int " sig ,
.BI "                      siginfo_t *" uinfo );
.BR rt_sigqueueinfo()
.BR rt_tgsigqueueinfo()
system calls are the low-level interfaces used to send a signal plus data
to a process or thread.
The receiver of the signal can obtain the accompanying data
by establishing a signal handler with the
.BR sigaction (2)

These system calls are not intended for direct application use;
they are provided to allow the implementation of
.BR sigqueue (3)
.BR pthread_sigqueue (3).

.BR rt_sigqueueinfo()
system call sends the signal
.I sig
to the thread group with the ID
.IR tgid .
(The term "thread group" is synonomous with "process", and
.I tid
corresponds to the traditional UNIX process ID.)
The signal will be delivered to an arbitrary member of the thread group
(i.e., one of the threads that is not currently blocking the signal).

.I uinfo
argument specifies the data to accompany the signal.
This argument is a pointer to a structure of type
.IR siginfo_t ,
described in
.BR sigaction (2)
(and defined by including
.IR <sigaction.h> ).
The caller should set the following fields in this structure:
.I si_code
This must be one of the
.B SI_*
codes in the kernel source file
.IR include/asm-generic/siginfo.h ,
with the restriction that the code must be negative
(i.e., cannot be
which is used by the kernel to indicate a signal sent by
.BR kill (2))
and cannot (since Linux 2.6.39) be
(which is used by the kernel to indicate a signal sent using
.\" tkill(2) or
.BR tgkill (2)).
.I si_pid
This should be set to a process ID,
typically the process ID of the sender.
.I si_uid
This should be set to a user ID,
typically the real user ID of the sender.
.I si_value
This field contains the user data to accompany the signal.
For more information, see the description of the last
.RI ( "union sigval" )
argument of
.BR sigqueue (3).
Internally, the kernel sets the
.I si_signo
field to the value specified in
.IR sig ,
so that the receiver of the signal can also obtain
the signal number via that field.

.BR rt_tgsigueueinfo ()
system call is like
.BR rt_sigueueinfo (),
but sends the signal and data to the single thread
specified by the combination of
.IR tgid ,
a thread group ID,
.IR tid ,
a thread in that thread group.
On success, these system calls return 0.
On error, they return \-1 and
.I errno
is set to indicate the error.
The limit of signals which may be queued has been reached.
.BR signal (7)
for further information.)
.IR sig ,
.IR tgid ,
.IR tid
was invalid.
The caller does not have permission to send the signal to the target.
For the required permissions, see
.BR kill (2).
.I uinfo->si_code
is invalid.
.BR rt_sigqueinfo ():
No thread group matching
.I tgid
was found.
.BR rt_rtsigqueinfo ():
No thread matching
.I tgid
.I tid
was found.
.BR rt_sigqueueinfo ()
system call was added to Linux in version 2.2.
.BR rt_tgsigqueueinfo ()
system call was added to Linux in version 2.6.31.
These system calls are Linux-specific.
Since these system calls are not intended for application use,
there are no glibc wrapper functions; use
.BR syscall (2)
in the unlikely case that you want to call them directly.

As with
.BR kill (2),
the null signal (0) can be used to check if the specified process
or thread exists.
.BR kill (2),
.BR sigaction (2),
.BR sigprocmask (2),
.BR tgkill (2),
.BR pthread_sigqueue (3),
.BR sigqueue (3),
.BR signal (7)

Michael Kerrisk
Linux man-pages maintainer;
Author of "The Linux Programming Interface";
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to
More majordomo info at

Copyright © 2011, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds