From: Oleg Nesterov <oleg@redhat.com>
To: guoren@kernel.org, Andrew Morton <akpm@linux-foundation.org>
Cc: linux-arch@vger.kernel.org, monstr@monstr.eu,
Guo Ren <guoren@linux.alibaba.com>,
arnd@arndb.de, linux@armlinux.org.uk,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
dinguyen@kernel.org, openrisc@lists.librecores.org,
palmer@dabbelt.com, vgupta@kernel.org,
sparclinux@vger.kernel.org, linux-snps-arc@lists.infradead.org,
davem@davemloft.net, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] arch: ptrace: Cleanup ptrace_disable
Date: Tue, 30 Aug 2022 16:20:07 +0200 [thread overview]
Message-ID: <20220830142006.GA20935@redhat.com> (raw)
In-Reply-To: <20220830065316.3924938-1-guoren@kernel.org>
On 08/30, guoren@kernel.org wrote:
>
> From: Guo Ren <guoren@linux.alibaba.com>
>
> This series cleanup ptrace_disable() in arch/*. Some architectures
> are duplicate clearing SYSCALL TRACE.
>
> Guo Ren (3):
> riscv: ptrace: Remove duplicate operation
> openrisc: ptrace: Remove duplicate operation
> arch: ptrace: Cleanup ptrace_disable
>
> arch/arc/kernel/ptrace.c | 4 ----
> arch/arm/kernel/ptrace.c | 8 --------
> arch/microblaze/kernel/ptrace.c | 5 -----
> arch/nios2/kernel/ptrace.c | 5 -----
> arch/openrisc/kernel/ptrace.c | 1 -
> arch/riscv/kernel/ptrace.c | 5 -----
> arch/sparc/kernel/ptrace_32.c | 10 ----------
> arch/sparc/kernel/ptrace_64.c | 10 ----------
> kernel/ptrace.c | 8 ++++++++
> 9 files changed, 8 insertions(+), 48 deletions(-)
Reviewed-by: Oleg Nesterov <oleg@redhat.com>
prev parent reply other threads:[~2022-08-30 14:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 6:53 [PATCH 0/3] arch: ptrace: Cleanup ptrace_disable guoren
2022-08-30 6:53 ` [PATCH 1/3] riscv: ptrace: Remove duplicate operation guoren
2022-08-30 6:53 ` [PATCH 2/3] openrisc: " guoren
2022-08-30 7:33 ` Stafford Horne
2022-08-30 6:53 ` [PATCH 3/3] arch: ptrace: Cleanup ptrace_disable guoren
2022-08-30 14:20 ` Oleg Nesterov [this message]
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=20220830142006.GA20935@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=dinguyen@kernel.org \
--cc=guoren@kernel.org \
--cc=guoren@linux.alibaba.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=monstr@monstr.eu \
--cc=openrisc@lists.librecores.org \
--cc=palmer@dabbelt.com \
--cc=sparclinux@vger.kernel.org \
--cc=vgupta@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).