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 <[email protected]> --- 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 <[email protected]>
