From: Jann Horn <jannh-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH] ptrace.2: copy retval info for SECCOMP_GET_FILTER to right section
Date: Thu, 8 Feb 2018 23:46:00 +0100 [thread overview]
Message-ID: <20180208224600.257982-1-jannh@google.com> (raw)
The "RETURN VALUE" section made a claim that was incorrect for
PTRACE_SECCOMP_GET_FILTER. Explicitly describe the behavior of
PTRACE_SECCOMP_GET_FILTER in the "RETURN VALUE" section (as usual), but
leave the now duplicate description in the section describing
PTRACE_SECCOMP_GET_FILTER, since the PTRACE_SECCOMP_GET_FILTER section
would otherwise probably become harder to understand.
Signed-off-by: Jann Horn <jannh-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
---
man2/ptrace.2 | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/man2/ptrace.2 b/man2/ptrace.2
index e1c3eec46..d78b8db2d 100644
--- a/man2/ptrace.2
+++ b/man2/ptrace.2
@@ -2206,7 +2206,10 @@ the report is sent only once.
On success, the
.B PTRACE_PEEK*
requests return the requested data (but see NOTES),
-while other requests return zero.
+the
+.B PTRACE_SECCOMP_GET_FILTER
+request returns the number of instructions in the BPF program, and
+other requests return zero.
.PP
On error, all requests return \-1, and
.I errno
--
2.16.0.rc1.238.g530d649a79-goog
--
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
next reply other threads:[~2018-02-08 22:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 22:46 Jann Horn [this message]
[not found] ` <20180208224600.257982-1-jannh-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2018-02-09 5:59 ` [PATCH] ptrace.2: copy retval info for SECCOMP_GET_FILTER to right section Michael Kerrisk (man-pages)
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=20180208224600.257982-1-jannh@google.com \
--to=jannh-hpiqsd4aklfqt0dzr+alfa@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@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