diff options
| author | Will Deacon <will@kernel.org> | 2026-07-17 17:25:58 +0100 |
|---|---|---|
| committer | Will Deacon <will@kernel.org> | 2026-07-17 17:25:58 +0100 |
| commit | 26b483d52417253d88a3a01262ac85914a7aec8e (patch) | |
| tree | 21c3a444fa80b1504e859922f2b4a34017a9636d /tools/perf/scripts/python/bin | |
| parent | f797f51a185ffdc1e3f915afed55f308b376842f (diff) | |
Revert "arm64: syscall: Ensure saved x0 is kept in-sync with tracer updates"
This reverts commit e057b94772328221405b067c3a85fe479b915dc8.
Sashiko points out that updating 'orig_x0' after secure_computing()
has returned is too late to handle the case where a seccomp filter is
re-evaluated after initially returning SECCOMP_RET_TRACE. This means
that a tracer can manipulate the first argument of the syscall behind
seccomp's back.
For now, revert the initial fix and we'll have another crack at it soon.
Since the incorrect fix was cc'd to stable, do the same here with an
appropriate fixes tag.
Cc: stable@vger.kernel.org
Fixes: e057b9477232 ("arm64: syscall: Ensure saved x0 is kept in-sync with tracer updates")
Link: https://sashiko.dev/#/patchset/20260716120640.6590-1-will@kernel.org
Signed-off-by: Will Deacon <will@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/bin')
0 files changed, 0 insertions, 0 deletions
