From: Stefan Liebler <stli@linux.vnet.ibm.com>
To: libc-alpha@sourceware.org
Subject: Re: [PATCH] S390: Sync ptrace.h with kernel. [BZ #21539]
Date: Thu, 08 Jun 2017 12:02:00 -0000 [thread overview]
Message-ID: <63ba9637-734e-e230-2b64-dea7caefe8c7@linux.vnet.ibm.com> (raw)
In-Reply-To: <49950192-7ab0-ebb8-b341-dcdfd3df2b87@linux.vnet.ibm.com>
On 06/06/2017 01:56 PM, Stefan Liebler wrote:
> On 06/06/2017 12:44 PM, Andreas Schwab wrote:
>> On Jun 06 2017, Stefan Liebler <stli@linux.vnet.ibm.com> wrote:
>>
>>> Hi,
>>>
>>> this patch removes PTRACE_GETREGS, PTRACE_SETREGS, PTRACE_GETFPREGS
>>> and PTRACE_SETFPREGS as these requests does not exist on s390 kernel.
>>
>> Since it is an API change it should probably get a NEWS entry.
>>
> I've added this NEWS entry:
> * The s390 specific ptrace requests are adjusted to the kernel ones.
> Request 12 is now used for PTRACE_SINGLEBLOCK instead of
> PTRACE_GETREGS. The requests PTRACE_GETREGS, PTRACE_SETREGS,
> PTRACE_GETFPREGS and PTRACE_SETFPREGS were removed as those are not
> supported by the s390 kernel. The requests PTRACE_SINGLEBLOCK,
> PTRACE_SECCOMP_GET_FILTER, PTRACE_PEEKUSR_AREA, PTRACE_POKEUSR_AREA,
> PTRACE_GET_LAST_BREAK, PTRACE_ENABLE_TE, PTRACE_DISABLE_TE and
> PTRACE_TE_ABORT_RAND were added as those are supported by the s390
> kernel.
>
Any objection?
Otherwise I'll commit the patch tomorrow.
Bye
Stefan
next prev parent reply other threads:[~2017-06-08 12:02 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-06 10:17 Stefan Liebler
2017-06-06 10:44 ` Andreas Schwab
2017-06-06 10:58 ` Dmitry V. Levin
2017-06-06 11:56 ` Stefan Liebler
2017-06-08 12:02 ` Stefan Liebler [this message]
2017-06-13 20:05 ` Dmitry V. Levin
2017-06-19 13:11 ` Stefan Liebler
2017-06-19 13:26 ` Dmitry V. Levin
2017-06-19 14:34 ` Stefan Liebler
2017-06-30 10:09 ` Florian Weimer
2017-07-04 8:22 ` Stefan Liebler
2017-07-04 9:41 ` Florian Weimer
2017-07-04 15:37 ` Stefan Liebler
2017-07-07 10:22 ` Stefan Liebler
2017-07-07 10:45 ` Florian Weimer
2017-07-07 13:54 ` Stefan Liebler
2017-07-11 8:39 ` Stefan Liebler
2017-07-18 10:20 ` Dmitry V. Levin
2017-07-18 13:31 ` Carlos O'Donell
2017-07-18 13:39 ` Dmitry V. Levin
2017-07-18 14:11 ` Carlos O'Donell
2017-07-18 14:28 ` Mark Wielaard
2017-07-18 14:40 ` Mark Wielaard
2017-07-20 7:38 ` Stefan Liebler
2017-07-20 8:07 ` Carlos O'Donell
2017-07-20 8:32 ` Stefan Liebler
2017-07-24 3:51 ` Dmitry V. Levin
2017-07-24 7:18 ` Stefan Liebler
2017-07-18 13:41 ` Stefan Liebler
2017-07-18 14:12 ` Carlos O'Donell
2017-07-18 14:16 ` Dmitry V. Levin
2017-07-19 8:40 ` Stefan Liebler
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=63ba9637-734e-e230-2b64-dea7caefe8c7@linux.vnet.ibm.com \
--to=stli@linux.vnet.ibm.com \
--cc=libc-alpha@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).