From: Will Deacon <will@kernel.org>
To: linux-arm-kernel@lists.infradead.org
Cc: linux-kernel@vger.kernel.org, Will Deacon <will@kernel.org>,
Kees Cook <kees@kernel.org>, Jinjie Ruan <ruanjinjie@huawei.com>,
Mark Rutland <mark.rutland@arm.com>
Subject: [PATCH v4 0/2] arm64: Fix handling of tracer updates to x0 on syscall entry
Date: Thu, 30 Jul 2026 14:26:49 +0100 [thread overview]
Message-ID: <20260730132651.25993-1-will@kernel.org> (raw)
Hi all,
This is version 4 of the patch previously posted here:
v1: https://lore.kernel.org/r/20260714143600.23853-1-will@kernel.org
v2: https://lore.kernel.org/r/20260716120640.6590-1-will@kernel.org
v3: https://lore.kernel.org/r/20260717182758.17111-1-will@kernel.org
Changes since v3 include:
- Add an additional patch to pass orig_x0 as the first syscall argument
for native tasks (Jinjie)
- Move WARN_ON_ONCE() after checking regs->syscallno (Sashiko)
- Add Tested-by from Jinjie.
Cheers,
Will
Cc: Kees Cook <kees@kernel.org>
Cc: Jinjie Ruan <ruanjinjie@huawei.com>
Cc: Mark Rutland <mark.rutland@arm.com>
--->8
Will Deacon (2):
arm64: ptrace: Keep 'orig_x0' in-sync with x0 on syscall entry
arm64: syscall: Pass 'orig_x0' as first argument to native system call
arch/arm64/include/asm/syscall_wrapper.h | 13 ++++--
arch/arm64/kernel/ptrace.c | 50 ++++++++++++++++++++++++
2 files changed, 59 insertions(+), 4 deletions(-)
--
2.55.0.508.g3f0d502094-goog
next reply other threads:[~2026-07-30 13:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 13:26 Will Deacon [this message]
2026-07-30 13:26 ` [PATCH v4 1/2] arm64: ptrace: Keep 'orig_x0' in-sync with x0 on syscall entry Will Deacon
2026-07-30 13:26 ` [PATCH v4 2/2] arm64: syscall: Pass 'orig_x0' as first argument to native system call Will Deacon
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=20260730132651.25993-1-will@kernel.org \
--to=will@kernel.org \
--cc=kees@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=ruanjinjie@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.