public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: Pavel Emelyanov <xemul@openvz.org>,
	Oleg Nesterov <oleg@tv-sign.ru>,
	Andrew Morton <akpm@linux-foundation.org>,
	Michael Kerrisk <mtk.manpages@gmail.com>,
	Kees Cook <keescook@chromium.org>, Jann Horn <jann@thejh.net>
Cc: Ted Estes <ted@softwarecrafters.com>,
	linux-man <linux-man@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: [Bug 210655] ptrace.2: documentation is incorrect about access checking threads in same thread group
Date: Tue, 15 Dec 2020 18:01:25 +0100	[thread overview]
Message-ID: <feef4f9a-4ed8-8a2e-d330-88e7f516faae@gmail.com> (raw)

Hi,

There's a bug report: https://bugzilla.kernel.org/show_bug.cgi?id=210655

[[
Under "Ptrace access mode checking", the documentation states:
  "1. If the calling thread and the target thread are in the same thread
group, access is always allowed."

This is incorrect. A thread may never attach to another in the same group.

Reference, ptrace_attach()
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/kernel/ptrace.c?h=v5.9.14#n380
]]

I just wanted to make sure that it is a bug in the manual page, and not
in the implementation.


Thanks,

Alex

-- 
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es

             reply	other threads:[~2020-12-15 17:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-15 17:01 Alejandro Colomar (man-pages) [this message]
2020-12-15 18:31 ` [Bug 210655] ptrace.2: documentation is incorrect about access checking threads in same thread group Ted Estes
2020-12-15 18:34   ` Alejandro Colomar (man-pages)
2020-12-15 22:48     ` Alejandro Colomar (man-pages)
2020-12-16  0:55       ` Linus Torvalds
2020-12-16  7:34         ` Oleg Nesterov
2020-12-15 23:07 ` Jann Horn
2020-12-15 23:23   ` Alejandro Colomar (man-pages)
2020-12-15 23:25     ` Alejandro Colomar (man-pages)
2020-12-16  0:01       ` Jann Horn
2020-12-16  2:21         ` Ted Estes
2020-12-16  2:33           ` Jann Horn
2020-12-16  9:22             ` Alejandro Colomar (man-pages)
2020-12-17 18:45               ` Eric W. Biederman

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=feef4f9a-4ed8-8a2e-d330-88e7f516faae@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=jann@thejh.net \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=oleg@tv-sign.ru \
    --cc=ted@softwarecrafters.com \
    --cc=xemul@openvz.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