From: Oleg Nesterov <oleg@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>,
Ted Estes <ted@softwarecrafters.com>,
Pavel Emelyanov <xemul@openvz.org>,
Andrew Morton <akpm@linux-foundation.org>,
Michael Kerrisk <mtk.manpages@gmail.com>,
Kees Cook <keescook@chromium.org>, Jann Horn <jann@thejh.net>,
linux-man <linux-man@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Markus Gutschke <markus@google.com>,
Roland McGrath <roland@redhat.com>,
Andreas Hobein <ah2@delair.de>
Subject: Re: [Bug 210655] ptrace.2: documentation is incorrect about access checking threads in same thread group
Date: Wed, 16 Dec 2020 08:34:16 +0100 [thread overview]
Message-ID: <20201216073415.GA19511@redhat.com> (raw)
In-Reply-To: <CAHk-=whppaJf=UoODaUP=tBjc9FjwSOX3hLBhZRgaGQKSKVW4A@mail.gmail.com>
On 12/15, Linus Torvalds wrote:
>
> On Tue, Dec 15, 2020 at 2:48 PM Alejandro Colomar (man-pages)
> <alx.manpages@gmail.com> wrote:
> >
> > 1) Remove that paragraph, as if that behavior had never existed.
>
> If it's been 15 years since that paragraph was relevant, I think just
> removing it is the right thing to do.
Agreed.
Oleg.
next prev parent reply other threads:[~2020-12-16 7:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 17:01 [Bug 210655] ptrace.2: documentation is incorrect about access checking threads in same thread group Alejandro Colomar (man-pages)
2020-12-15 18:31 ` 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 [this message]
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=20201216073415.GA19511@redhat.com \
--to=oleg@redhat.com \
--cc=ah2@delair.de \
--cc=akpm@linux-foundation.org \
--cc=alx.manpages@gmail.com \
--cc=jann@thejh.net \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=markus@google.com \
--cc=mtk.manpages@gmail.com \
--cc=roland@redhat.com \
--cc=ted@softwarecrafters.com \
--cc=torvalds@linux-foundation.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.