From: Will Deacon <will@kernel.org>
To: linux-arm-kernel@lists.infradead.org, Will Deacon <will@kernel.org>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
linux-kernel@vger.kernel.org, Kees Cook <kees@kernel.org>,
Jinjie Ruan <ruanjinjie@huawei.com>,
Mark Rutland <mark.rutland@arm.com>,
Yiqi Sun <sunyiqixm@gmail.com>
Subject: Re: [PATCH v2] arm64: syscall: Ensure saved x0 is kept in-sync with tracer updates
Date: Thu, 16 Jul 2026 17:48:01 +0100 [thread overview]
Message-ID: <178420908877.33796.2351583216856259313.b4-ty@kernel.org> (raw)
In-Reply-To: <20260716120640.6590-1-will@kernel.org>
On Thu, 16 Jul 2026 13:06:39 +0100, Will Deacon wrote:
> When seccomp support was originally added to arm64 in a1ae65b21941
> ("arm64: add seccomp support"), seccomp was erroneously called _before_
> the ptrace syscall-enter-stop and therefore the tracer could trivially
> manipulate the syscall register state after the seccomp check had
> passed. This was subsequently fixed in a5cd110cb836 ("arm64/ptrace: run
> seccomp after ptrace") by moving the seccomp check after the tracer has
> run. Unfortunately, a decade later, that fix has been reported to be
> incomplete.
>
> [...]
Applied to arm64 (for-next/fixes), thanks!
[1/1] arm64: syscall: Ensure saved x0 is kept in-sync with tracer updates
https://git.kernel.org/arm64/c/e057b9477232
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
next prev parent reply other threads:[~2026-07-16 16:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 12:06 [PATCH v2] arm64: syscall: Ensure saved x0 is kept in-sync with tracer updates Will Deacon
2026-07-16 12:28 ` Jinjie Ruan
2026-07-16 16:48 ` Will Deacon [this message]
2026-07-17 17:54 ` Will Deacon
2026-07-20 3:48 ` Jinjie Ruan
2026-07-21 14:05 ` Will Deacon
2026-07-23 4:12 ` Jinjie Ruan
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=178420908877.33796.2351583216856259313.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kees@kernel.org \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=ruanjinjie@huawei.com \
--cc=sunyiqixm@gmail.com \
/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