From: Oleg Nesterov <oleg@redhat.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>,
Jann Horn <jann@thejh.net>, James Morris <jmorris@namei.org>,
linux-man <linux-man@vger.kernel.org>,
Stephen Smalley <sds@tycho.nsa.gov>,
lkml <linux-kernel@vger.kernel.org>,
Kees Cook <keescook@chromium.org>,
linux-security-module <linux-security-module@vger.kernel.org>,
Linux API <linux-api@vger.kernel.org>
Subject: Re: Documenting ptrace access mode checking
Date: Wed, 22 Jun 2016 23:51:42 +0200 [thread overview]
Message-ID: <20160622215142.GA14751@redhat.com> (raw)
In-Reply-To: <87ziqewc3r.fsf@x220.int.ebiederm.org>
On 06/21, Eric W. Biederman wrote:
>
> Adding Oleg just because he seems to do most of the ptrace related
> maintenance these days.
so I have to admit that I never even tried to actually understand
ptrace_may_access ;)
> We certainly need something that gives a high level view so people
> reading the man page can know what to expect. If you get down into the
> weeds we run the danger of people beginning to think they can depend
> upon bugs in the implementation.
Personally I agree. I think "man ptrace" shouldn't not tell too much
about kernel internals.
Perhaps Documentation/security/ makes more sense?
Oleg.
next prev parent reply other threads:[~2016-06-22 21:51 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 9:41 Michael Kerrisk (man-pages)
2016-06-21 19:55 ` Eric W. Biederman
2016-06-21 20:29 ` Kees Cook
2016-06-21 20:58 ` Eric W. Biederman
2016-06-22 19:20 ` Michael Kerrisk (man-pages)
2016-06-22 19:20 ` Michael Kerrisk (man-pages)
2016-06-23 19:04 ` Eric W. Biederman
2016-06-24 9:57 ` Michael Kerrisk (man-pages)
2016-06-22 21:51 ` Oleg Nesterov [this message]
2016-06-23 7:06 ` Michael Kerrisk (man-pages)
2016-06-23 18:56 ` Eric W. Biederman
2016-06-24 8:18 ` Michael Kerrisk (man-pages)
2016-06-21 20:55 ` Jann Horn
2016-06-22 19:21 ` Michael Kerrisk (man-pages)
2016-06-22 21:11 ` Kees Cook
2016-06-23 7:02 ` Michael Kerrisk (man-pages)
2016-06-24 8:40 ` Michael Kerrisk (man-pages)
2016-06-24 15:18 ` Casey Schaufler
2016-06-24 20:07 ` Kees Cook
2016-06-25 7:21 ` Michael Kerrisk (man-pages)
2016-06-22 22:44 ` Jann Horn
2016-06-23 7:42 ` Michael Kerrisk (man-pages)
2016-06-24 6:35 ` Jann Horn
2016-06-23 18:05 ` Stephen Smalley
2016-06-24 8:33 ` 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=20160622215142.GA14751@redhat.com \
--to=oleg@redhat.com \
--cc=ebiederm@xmission.com \
--cc=jann@thejh.net \
--cc=jmorris@namei.org \
--cc=keescook@chromium.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=sds@tycho.nsa.gov \
/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
Powered by JetHome