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>
Subject: Re: [PATCH v4 0/2] arm64: Fix handling of tracer updates to x0 on syscall entry
Date: Sun, 2 Aug 2026 13:12:35 +0100 [thread overview]
Message-ID: <178566435675.4143863.9174179007442722052.b4-ty@kernel.org> (raw)
In-Reply-To: <20260730132651.25993-1-will@kernel.org>
On Thu, 30 Jul 2026 14:26:49 +0100, Will Deacon wrote:
> 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:
>
> [...]
I decided against applying these for v7.2 this late in the cycle, so
I've queued them up for v7.3 for some more exposure.
Applied to arm64 (for-next/ptrace), thanks!
[1/2] arm64: ptrace: Keep 'orig_x0' in-sync with x0 on syscall entry
https://git.kernel.org/arm64/c/88b839ce497c
[2/2] arm64: syscall: Pass 'orig_x0' as first argument to native system call
https://git.kernel.org/arm64/c/5a87e8c7f370
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2026-08-02 12:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 13:26 Will Deacon
2026-07-30 13:26 ` [PATCH v4 1/2] arm64: ptrace: Keep 'orig_x0' in-sync with " 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
2026-08-02 12:12 ` Will Deacon [this message]
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=178566435675.4143863.9174179007442722052.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 \
/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
all inboxes | Powered by JetHome®