From: Oleg Nesterov <oleg@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
Andrew Morton <akpm@linux-foundation.org>,
Eugene Syromiatnikov <esyr@redhat.com>,
Jan Kratochvil <jan.kratochvil@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Michael Kerrisk <mtk.manpages@gmail.com>,
Simon Marchi <simon.marchi@efficios.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] ptrace: make ptrace() fail if the tracee changed its pid unexpectedly
Date: Sat, 19 Dec 2020 20:33:14 +0100 [thread overview]
Message-ID: <20201219193313.GB9539@redhat.com> (raw)
In-Reply-To: <fc796624-2660-8c2b-0956-2c9ba8281952@redhat.com>
On 12/19, Pedro Alves wrote:
>
> BTW, the problem was discovered by Simon Marchi when he tried to write
> a GDB testcase for a multi-threaded exec scenario:
OOPS! Sorry Simon, yes I forgot to add reported-by. Andrew, or Eric, if
you take this patch, could you also add
Reported-by: Simon Marchi <simon.marchi@efficios.com>
> I've went through GDB's code looking for potential issues with the change and whether
> it would affect GDBs already in the wild. Tricky corner cases abound, but I think
> we're good. Feel free to add my ack:
>
> Acked-by: Pedro Alves <palves@redhat.com>
Thanks!
Oleg.
next prev parent reply other threads:[~2020-12-19 19:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 14:29 [RFC PATCH] ptrace: make ptrace() fail if the tracee changed its pid unexpectedly Oleg Nesterov
2020-12-17 23:39 ` Eric W. Biederman
2020-12-18 14:10 ` Oleg Nesterov
2020-12-21 20:04 ` Eric W. Biederman
2020-12-19 16:19 ` Pedro Alves
2020-12-19 19:33 ` Oleg Nesterov [this message]
2020-12-20 4:48 ` Simon Marchi
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=20201219193313.GB9539@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=esyr@redhat.com \
--cc=jan.kratochvil@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mtk.manpages@gmail.com \
--cc=palves@redhat.com \
--cc=simon.marchi@efficios.com \
--cc=torvalds@linux-foundation.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.