From: Jinjie Ruan <ruanjinjie@huawei.com>
To: Will Deacon <will@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, Kees Cook <kees@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Yiqi Sun <sunyiqixm@gmail.com>,
Catalin Marinas <catalin.marinas@arm.com>
Subject: Re: [PATCH] arm64: syscall: Ensure saved x0 is kept in-sync with tracer updates
Date: Thu, 16 Jul 2026 20:04:17 +0800 [thread overview]
Message-ID: <afcd731c-f304-460b-9552-a0d9c9ab5a82@huawei.com> (raw)
In-Reply-To: <aljGHQW92uz1HAwI@willie-the-truck>
On 7/16/2026 7:53 PM, Will Deacon wrote:
> On Thu, Jul 16, 2026 at 10:57:34AM +0800, Jinjie Ruan wrote:
>> On 7/14/2026 10:35 PM, Will Deacon wrote:
>>> diff --git a/arch/arm64/kernel/ptrace.c b/arch/arm64/kernel/ptrace.c
>>> index 4d08598e2891..57e8c6714d44 100644
>>> --- a/arch/arm64/kernel/ptrace.c
>>> +++ b/arch/arm64/kernel/ptrace.c
>>> @@ -2408,6 +2408,21 @@ static void report_syscall_exit(struct pt_regs *regs)
>>> }
>>> }
>>>
>>> +static void update_syscall_orig_x0_after_ptrace(struct pt_regs *regs)
>>> +{
>>> + /*
>>> + * Keep orig_x0 authoritative so that seccomp (via
>>> + * syscall_get_arguments()), audit and the restart path all see the same
>>> + * first argument the syscall is dispatched with, even if it has been
>>> + * updated by a tracer. Skip this for NO_SYSCALL (set either by the user
>>> + * or the tracer), as regs[0] holds the return value (see the comment in
>>> + * el0_svc_common()) and can be unwound using syscall_rollback().
>>> + * For compat tasks, orig_r0 is provided directly through GPR index 17.
>>> + */
>>> + if (!is_compat_task() && regs->syscallno != NO_SYSCALL)
>>> + regs->orig_x0 = regs->regs[0];
>>> +}
>>> +
>>> int syscall_trace_enter(struct pt_regs *regs)
>>> {
>>> unsigned long flags = read_thread_flags();
>>> @@ -2417,12 +2432,21 @@ int syscall_trace_enter(struct pt_regs *regs)
>>> ret = report_syscall_entry(regs);
>>> if (ret || (flags & _TIF_SYSCALL_EMU))
>>> return NO_SYSCALL;
>>> +
>>> + /*
>>> + * Ensure ptrace changes to x0 are visible to seccomp
>>> + * ptrace exits (SECCOMP_RET_TRACE).
>>> + */
>>> + update_syscall_orig_x0_after_ptrace(regs);
>>> }
>>>
>>> /* Do the secure computing after ptrace; failures should be fast. */
>>> if (secure_computing() == -1)
>>> return NO_SYSCALL;
>>>
>>> + /* Ensure seccomp updates to x0 are visible to audit. */
>>> + update_syscall_orig_x0_after_ptrace(regs);
>>
>> I think unconditionally updating orig_x0 here is unnecessary, we could
>> Expand seccomp check in place as below the same as generic entry.
>
> Let's leave any micro-optimisations for later, please. We're going to
That sounds good. We can make these changes that are not closely related
to this fix when we switch to the generic entry.
> need to backport this fix _way_ back, so I've been trying to keep it as
> simple as possible. You're also going to end up replacing all of this
> with the generic entry code, anyway.
>
> I'll send a v2 with the comment changes shortly, then hopefully I can
> send it as a fix for stable.
Thanks for the update. If v2 comes out, I am happy to help test it again.
>
> Thanks,
>
> Will
next prev parent reply other threads:[~2026-07-16 12:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 14:35 [PATCH] arm64: syscall: Ensure saved x0 is kept in-sync with tracer updates Will Deacon
2026-07-15 11:39 ` Jinjie Ruan
2026-07-15 13:16 ` Will Deacon
2026-07-16 2:09 ` Jinjie Ruan
2026-07-16 11:50 ` Will Deacon
2026-07-16 2:57 ` Jinjie Ruan
2026-07-16 3:05 ` Kees Cook
2026-07-16 3:25 ` Jinjie Ruan
2026-07-16 11:53 ` Will Deacon
2026-07-16 12:04 ` Jinjie Ruan [this message]
2026-08-20 6:54 ` kernel test robot
2026-08-20 11:25 ` kernel test robot
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=afcd731c-f304-460b-9552-a0d9c9ab5a82@huawei.com \
--to=ruanjinjie@huawei.com \
--cc=catalin.marinas@arm.com \
--cc=kees@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=sunyiqixm@gmail.com \
--cc=will@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