On Thu, 10 Sep 2026 20:00:39 +0100, Mark Brown wrote:
> 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.
Applied to arm64 (for-next/gcs), thanks!
While a minor ABI change, it's pretty harmless. The benfit is eventual
(hopefully) common handling with x86 and risc-v. I did wonder whether to
cc stable but we can always send it separately.
[1/2] arm64: gcs: Return -EPERM not -EBUSY for prctl() locking failures
https://git.kernel.org/arm64/c/988be99717ae
[2/2] kselftest/arm64: Check for -EPERM not -EBUSY in the locking test
https://git.kernel.org/arm64/c/8c831e5cd3ad