From: Will Deacon <will@kernel.org>
To: linux-trace-kernel@vger.kernel.org,
Jeremy Linton <jeremy.linton@arm.com>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
linux-perf-users@vger.kernel.org, mhiramat@kernel.org,
oleg@redhat.com, peterz@infradead.org, mingo@redhat.com,
acme@kernel.org, namhyung@kernel.org, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, jolsa@kernel.org,
irogers@google.com, adrian.hunter@intel.com,
kan.liang@linux.intel.com, thiago.bauermann@linaro.org,
broonie@kernel.org, yury.khrustalev@arm.com,
kristina.martsenko@arm.com, liaochang1@huawei.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 0/7] arm64: Enable UPROBES with GCS
Date: Tue, 16 Sep 2025 22:13:49 +0100 [thread overview]
Message-ID: <175805110604.263842.2881563818650081445.b4-ty@kernel.org> (raw)
In-Reply-To: <20250825033421.463669-1-jeremy.linton@arm.com>
On Sun, 24 Aug 2025 22:34:14 -0500, Jeremy Linton wrote:
> Currently uprobes and the Arm Guarded Control Stack (GCS) feature are
> exclusive of each other. This restriction needs to be lifted in order
> to utilize GCS for generic Linux distro images where the expectation
> is that core debugging features like uprobes work.
>
> This series adds some user accessors to read/push/pop the userspace
> shadow stack. It then utilizes those functions in the uprobe paths as
> needed to synchronize GCS with the changes in control flow at probe
> locations.
>
> [...]
Applied to arm64 (for-next/uprobes), thanks!
[1/7] arm64: probes: Break ret out from bl/blr
https://git.kernel.org/arm64/c/47687aa4d9c9
[2/7] arm64: uaccess: Move existing GCS accessors definitions to gcs.h
https://git.kernel.org/arm64/c/ea920b50ac9f
[3/7] arm64: uaccess: Add additional userspace GCS accessors
https://git.kernel.org/arm64/c/9cd2a7f1180f
[4/7] arm64: probes: Add GCS support to bl/blr/ret
https://git.kernel.org/arm64/c/efb07ac534e2
[5/7] arm64: uprobes: Add GCS support to uretprobes
https://git.kernel.org/arm64/c/4a601714bb24
[6/7] arm64: Kconfig: Remove GCS restrictions on UPROBES
https://git.kernel.org/arm64/c/cc66c711e58f
[7/7] uprobes: uprobe_warn should use passed task
https://git.kernel.org/arm64/c/ba1afc94deb8
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2025-09-16 21:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-25 3:34 [PATCH v7 0/7] arm64: Enable UPROBES with GCS Jeremy Linton
2025-08-25 3:34 ` [PATCH v7 1/7] arm64: probes: Break ret out from bl/blr Jeremy Linton
2025-08-25 3:34 ` [PATCH v7 2/7] arm64: uaccess: Move existing GCS accessors definitions to gcs.h Jeremy Linton
2025-08-25 3:34 ` [PATCH v7 3/7] arm64: uaccess: Add additional userspace GCS accessors Jeremy Linton
2025-08-25 3:34 ` [PATCH v7 4/7] arm64: probes: Add GCS support to bl/blr/ret Jeremy Linton
2025-09-18 12:54 ` Jeremy Linton
2025-09-18 13:56 ` Will Deacon
2025-08-25 3:34 ` [PATCH v7 5/7] arm64: uprobes: Add GCS support to uretprobes Jeremy Linton
2025-08-25 3:34 ` [PATCH v7 6/7] arm64: Kconfig: Remove GCS restrictions on UPROBES Jeremy Linton
2025-08-25 3:34 ` [PATCH v7 7/7] uprobes: uprobe_warn should use passed task Jeremy Linton
2025-09-16 21:13 ` 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=175805110604.263842.2881563818650081445.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=irogers@google.com \
--cc=jeremy.linton@arm.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=kernel-team@android.com \
--cc=kristina.martsenko@arm.com \
--cc=liaochang1@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=thiago.bauermann@linaro.org \
--cc=yury.khrustalev@arm.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