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>
Subject: [PATCH 2/2] kselftest/arm64: Check for -EPERM not -EBUSY in the locking test
Date: Thu, 10 Sep 2026 20:00:41 +0100 [thread overview]
Message-ID: <20260910-arm64-gcs-lock-eperm-v1-2-d88e51855c9f@kernel.org> (raw)
In-Reply-To: <20260910-arm64-gcs-lock-eperm-v1-0-d88e51855c9f@kernel.org>
The API has been updated to return the more permissive -EPERM rather
than -EBUSY, update the selftest to reflect this.
Signed-off-by: Mark Brown <broonie@kernel.org>
---
tools/testing/selftests/arm64/gcs/gcs-locking.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/testing/selftests/arm64/gcs/gcs-locking.c b/tools/testing/selftests/arm64/gcs/gcs-locking.c
index 1e6abb136ffd..f780f0c7b8dd 100644
--- a/tools/testing/selftests/arm64/gcs/gcs-locking.c
+++ b/tools/testing/selftests/arm64/gcs/gcs-locking.c
@@ -115,7 +115,7 @@ TEST_F(valid_modes, enable_lock_disable)
ASSERT_EQ(ret, 0);
ret = my_syscall2(__NR_prctl, PR_SET_SHADOW_STACK_STATUS, 0);
- ASSERT_EQ(ret, -EBUSY);
+ ASSERT_EQ(ret, -EPERM);
_exit(0);
}
@@ -131,7 +131,7 @@ TEST_F(valid_modes, lock_enable)
ret = my_syscall2(__NR_prctl, PR_SET_SHADOW_STACK_STATUS,
variant->mode);
- ASSERT_EQ(ret, -EBUSY);
+ ASSERT_EQ(ret, -EPERM);
ret = prctl(PR_GET_SHADOW_STACK_STATUS, &mode, 0, 0, 0);
ASSERT_EQ(ret, 0);
--
2.47.3
next prev parent reply other threads:[~2026-09-10 19:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 19:00 [PATCH 0/2] arm64: gcs: Return -EPERM when changes are prevented by locking Mark Brown
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 ` Mark Brown [this message]
2026-10-06 14:42 ` [PATCH 2/2] kselftest/arm64: Check for -EPERM not -EBUSY in the locking test Catalin Marinas
2026-10-06 15:01 ` Mark Brown
2026-10-06 14:40 ` [PATCH 0/2] arm64: gcs: Return -EPERM when changes are prevented by locking Catalin Marinas
2026-10-06 15:15 ` Mark Brown
2026-09-24 20:49 ` Bill Roberts
2026-10-06 16:31 ` Mark Brown
2026-09-25 1:55 ` Bill Roberts
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-2-d88e51855c9f@kernel.org \
--to=broonie@kernel.org \
--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
all inboxes | Powered by JetHome®