From: guoren@kernel.org
To: oleg@redhat.com, vgupta@kernel.org, linux@armlinux.org.uk,
monstr@monstr.eu, dinguyen@kernel.org, palmer@dabbelt.com,
davem@davemloft.net, arnd@arndb.de, shorne@gmail.com,
guoren@kernel.org
Cc: linux-arch@vger.kernel.org, Guo Ren <guoren@linux.alibaba.com>,
linux-kernel@vger.kernel.org, openrisc@lists.librecores.org,
sparclinux@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-snps-arc@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 0/3] arch: Cleanup ptrace_disable
Date: Sat, 3 Sep 2022 12:23:24 -0400 [thread overview]
Message-ID: <20220903162328.1952477-1-guoren@kernel.org> (raw)
From: Guo Ren <guoren@linux.alibaba.com>
This series cleanup ptrace_disable() in arch/*. Some architectures
are duplicate clearing SYSCALL TRACE.
Changes in V2:
- Rebase on linux-6.0-rc3
- Add Reviewed-by tags.
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(-)
--
2.36.1
next reply other threads:[~2022-09-03 16:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-03 16:23 guoren [this message]
2022-09-03 16:23 ` [PATCH V2 1/3] riscv: ptrace: Remove duplicate operation guoren
2022-09-03 16:23 ` [PATCH V2 2/3] openrisc: " guoren
2022-09-03 16:23 ` [PATCH V2 3/3] arch: ptrace: Cleanup ptrace_disable guoren
2022-09-03 16:23 ` [PATCH] RISC-V: Add STACKLEAK erasing the kernel stack at the end of syscalls guoren
2022-09-06 17:35 ` Conor.Dooley
2022-09-07 1:51 ` Guo Ren
2022-10-07 2:31 ` Palmer Dabbelt
2022-10-07 11:29 ` Mark Rutland
2022-10-08 0:00 ` Guo Ren
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=20220903162328.1952477-1-guoren@kernel.org \
--to=guoren@kernel.org \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=dinguyen@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=oleg@redhat.com \
--cc=openrisc@lists.librecores.org \
--cc=palmer@dabbelt.com \
--cc=shorne@gmail.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).