[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <175328660445.3870926.2919716092405832672.b4-ty@arm.com>
Date: Wed, 23 Jul 2025 17:03:34 +0100
From: Catalin Marinas <catalin.marinas@....com>
To: linux-trace-kernel@...r.kernel.org,
Jeremy Linton <jeremy.linton@....com>
Cc: Will Deacon <will@...nel.org>,
linux-perf-users@...r.kernel.org,
mhiramat@...nel.org,
oleg@...hat.com,
peterz@...radead.org,
acme@...nel.org,
namhyung@...nel.org,
mark.rutland@....com,
alexander.shishkin@...ux.intel.com,
jolsa@...nel.org,
irogers@...gle.com,
adrian.hunter@...el.com,
kan.liang@...ux.intel.com,
thiago.bauermann@...aro.org,
broonie@...nel.org,
yury.khrustalev@....com,
kristina.martsenko@....com,
liaochang1@...wei.com,
linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: (subset) [PATCH v4 0/8] arm64: Enable UPROBES with GCS
On Fri, 18 Jul 2025 23:37:32 -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/misc), thanks!
[1/8] arm64/gcs: task_gcs_el0_enable() should use passed task
https://git.kernel.org/arm64/c/cbbcfb94c55c
--
Catalin
Powered by blists - more mailing lists