From: Pedro Alves <palves@redhat.com>
To: Andy Lutomirski <luto@kernel.org>, x86@kernel.org
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Kees Cook <keescook@chromium.org>, Borislav Petkov <bp@alien8.de>,
Oleg Nesterov <oleg@redhat.com>
Subject: Re: [PATCH] x86/ptrace: Remove questionable TS_COMPAT usage in ptrace
Date: Sat, 18 Jun 2016 15:41:15 +0100 [thread overview]
Message-ID: <5fd9818c-4bf5-753a-535c-b03c2dfaad47@redhat.com> (raw)
In-Reply-To: <b9f316ca-5f79-91f5-1d19-773679778357@palves.net>
On 06/18/2016 02:55 PM, Pedro Alves wrote:
> This hunk being mentioned in this thread a couple years ago too:
>
> https://www.sourceware.org/ml/gdb/2014-04/msg00095.html
>
> Please don't break this use case ( and fix the one reported in
> that thread :-) ).
BTW, there was a follow up v2 patch to that last url, here:
[PATCH v2] Fix get ERESTARTSYS with m32 in x86_64 when debug by GDB
https://sourceware.org/ml/gdb/2014-05/msg00004.html
(for some reason, I can only find the ping on the lkml, not the
original post, though it was apparently CCed.)
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-06-18 14:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-18 10:21 Andy Lutomirski
2016-06-18 13:55 ` Pedro Alves
2016-06-18 14:41 ` Pedro Alves [this message]
2016-06-18 17:02 ` Andy Lutomirski
2016-06-19 22:09 ` Andy Lutomirski
2016-06-20 10:27 ` Pedro Alves
2016-06-20 15:24 ` Oleg Nesterov
2016-06-20 16:30 ` Andy Lutomirski
2016-06-20 16:14 ` Oleg Nesterov
2016-06-20 17:25 ` Andy Lutomirski
2016-06-20 10:07 ` Pedro Alves
2016-06-20 11:12 ` Jan Kratochvil
2016-06-18 17:48 ` Kees Cook
2016-06-19 21:19 ` Oleg Nesterov
2016-06-19 22:23 ` Andy Lutomirski
2016-06-20 6:12 ` Andy Lutomirski
2016-06-20 15:31 ` Oleg Nesterov
2016-06-20 17:53 ` the usage of __SYSCALL_MASK in entry_SYSCALL_64/do_syscall_64 is not consistent Oleg Nesterov
2016-06-21 19:01 ` Kees Cook
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=5fd9818c-4bf5-753a-535c-b03c2dfaad47@redhat.com \
--to=palves@redhat.com \
--cc=bp@alien8.de \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=oleg@redhat.com \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®