From: Mark Brown <broonie@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Shuah Khan <shuah@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
Mark Brown <broonie@kernel.org>,
Bill Roberts <bill.roberts@foss.arm.com>
Subject: [PATCH 0/2] arm64: gcs: Return -EPERM when changes are prevented by locking
Date: Thu, 10 Sep 2026 20:00:39 +0100 [thread overview]
Message-ID: <20260910-arm64-gcs-lock-eperm-v1-0-d88e51855c9f@kernel.org> (raw)
When we refuse to change the GCS configuraiton due to locking we
currently return -EBUSY which is an odd choice. The only userspace I
found that relies on this value at present is the kselftest and other
architectures are using the more obvious -EPERM here let's switch.
Signed-off-by: Mark Brown <broonie@kernel.org>
---
Mark Brown (2):
arm64: gcs: Return -EPERM not -EBUSY for prctl() locking failures
kselftest/arm64: Check for -EPERM not -EBUSY in the locking test
arch/arm64/include/asm/gcs.h | 2 +-
tools/testing/selftests/arm64/gcs/gcs-locking.c | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
---
base-commit: df2908090cda368b01ff43709f51890076c56157
change-id: 20260910-arm64-gcs-lock-eperm-06ce8f8e5250
Best regards,
--
Mark Brown <broonie@kernel.org>
next reply other threads:[~2026-09-10 19:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 19:00 Mark Brown [this message]
2026-09-10 19:00 ` [PATCH 1/2] arm64: gcs: Return -EPERM not -EBUSY for prctl() locking failures Mark Brown
2026-09-10 19:00 ` [PATCH 2/2] kselftest/arm64: Check for -EPERM not -EBUSY in the locking test Mark Brown
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=20260910-arm64-gcs-lock-eperm-v1-0-d88e51855c9f@kernel.org \
--to=broonie@kernel.org \
--cc=bill.roberts@foss.arm.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=shuah@kernel.org \
--cc=will@kernel.org \
/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