From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Andrey Vagin <avagin-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
criu-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org
Subject: Re: [PATCH 3/3] ptrace.2: add description for PTRACE_{GET,SET}SIGMASK
Date: Mon, 20 Jan 2014 11:03:40 +0100 [thread overview]
Message-ID: <52DCF47C.6040200@gmail.com> (raw)
In-Reply-To: <1373962773-2041-4-git-send-email-avagin-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
On 07/16/2013 10:19 AM, Andrey Vagin wrote:
> These two commands allow to examine and change mask of blocked signals.
Thanks, Andrey.
Applied.
Cheers,
Michael
> Signed-off-by: Andrey Vagin <avagin-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
> ---
> man2/ptrace.2 | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/man2/ptrace.2 b/man2/ptrace.2
> index e74535e..08697ff 100644
> --- a/man2/ptrace.2
> +++ b/man2/ptrace.2
> @@ -356,6 +356,21 @@ If this flag is not set, signals are read from a per-thread queue.
> .in
> .PP
> .TP
> +.BR PTRACE_GETSIGMASK " (since Linux 3.11)"
> +.\" commit 29000caecbe87b6b66f144f72111f0d02fbbf0c1
> +Retrieve mask of blocked signals to the address
> +.I data.
> +The
> +.I addr
> +argument contains the size of mask.
> +.TP
> +.BR PTRACE_SETSIGMASK " (since Linux 3.11)"
> +Change mask of blocked signals from the address
> +.I data.
> +The
> +.I addr
> +argument contains the size of mask.
> +.TP
> .BR PTRACE_SETOPTIONS " (since Linux 2.4.6; see BUGS for caveats)"
> Set ptrace options from
> .IR data .
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2014-01-20 10:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 8:19 [PATCH 0/3] ptrace.2: explain new commands to work with signals Andrey Vagin
2013-07-16 8:19 ` [PATCH 1/3] ptrace.2: place GETSIGINFO and SETSIGINFO near each other Andrey Vagin
[not found] ` <1373962773-2041-2-git-send-email-avagin-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2013-07-18 1:13 ` Michael Kerrisk
[not found] ` <51E74143.4040709-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-08-08 14:43 ` Andrew Vagin
2013-07-16 8:19 ` [PATCH 2/3] ptrace.2: add description for PTRACE_PEEKSIGINFO Andrey Vagin
[not found] ` <1373962773-2041-3-git-send-email-avagin-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2014-01-20 10:02 ` Michael Kerrisk (man-pages)
2013-07-16 8:19 ` [PATCH 3/3] ptrace.2: add description for PTRACE_{GET,SET}SIGMASK Andrey Vagin
[not found] ` <1373962773-2041-4-git-send-email-avagin-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2014-01-20 10:03 ` Michael Kerrisk (man-pages) [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=52DCF47C.6040200@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=avagin-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org \
--cc=criu-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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;
as well as URLs for NNTP newsgroup(s).