From: Stafford Horne <shorne@gmail.com>
To: guoren@kernel.org
Cc: 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, linux-arch@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-snps-arc@lists.infradead.org, sparclinux@vger.kernel.org,
openrisc@lists.librecores.org, Guo Ren <guoren@linux.alibaba.com>
Subject: Re: [PATCH 2/3] openrisc: ptrace: Remove duplicate operation
Date: Tue, 30 Aug 2022 07:33:51 +0000 [thread overview]
Message-ID: <Yw29XwOoUY1Foze/@oscomms1> (raw)
In-Reply-To: <20220830065316.3924938-3-guoren@kernel.org>
On Tue, Aug 30, 2022 at 02:53:15AM -0400, guoren@kernel.org wrote:
> From: Guo Ren <guoren@linux.alibaba.com>
>
> The TIF_SYSCALL_TRACE is controlled by a common code, see
> kernel/ptrace.c and include/linux/thread.h.
>
> clear_task_syscall_work(child, SYSCALL_TRACE);
>
> Signed-off-by: Guo Ren <guoren@linux.alibaba.com>
> Signed-off-by: Guo Ren <guoren@kernel.org>
Acked-by: Stafford Horne <shorne@gmail.com>
> ---
> arch/openrisc/kernel/ptrace.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/arch/openrisc/kernel/ptrace.c b/arch/openrisc/kernel/ptrace.c
> index b971740fc2aa..cc53fa676706 100644
> --- a/arch/openrisc/kernel/ptrace.c
> +++ b/arch/openrisc/kernel/ptrace.c
> @@ -132,7 +132,6 @@ void ptrace_disable(struct task_struct *child)
> pr_debug("ptrace_disable(): TODO\n");
>
> user_disable_single_step(child);
> - clear_tsk_thread_flag(child, TIF_SYSCALL_TRACE);
> }
>
> long arch_ptrace(struct task_struct *child, long request, unsigned long addr,
> --
> 2.36.1
>
next prev parent reply other threads:[~2022-08-30 7:33 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 [this message]
2022-08-30 6:53 ` [PATCH 3/3] arch: ptrace: Cleanup ptrace_disable guoren
2022-08-30 14:20 ` [PATCH 0/3] " Oleg Nesterov
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=Yw29XwOoUY1Foze/@oscomms1 \
--to=shorne@gmail.com \
--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=oleg@redhat.com \
--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 NNTP newsgroup(s).