alarmtimer: Use EOPNOTSUPP instead of ENOTSUPP
authorThadeu Lima de Souza Cascardo <cascardo@canonical.com>
Tue, 3 Sep 2019 17:18:02 +0000 (14:18 -0300)
committerThomas Gleixner <tglx@linutronix.de>
Thu, 5 Sep 2019 19:19:26 +0000 (21:19 +0200)
commitf18ddc13af981ce3c7b7f26925f099e7c6929aba
treeee642b2934ba01c1e5ee4f367bde2340abdef4b7
parent3b47fd5ca9ead91156bcdf6435279ad0b14a650c
alarmtimer: Use EOPNOTSUPP instead of ENOTSUPP

ENOTSUPP is not supposed to be returned to userspace. This was found on an
OpenPower machine, where the RTC does not support set_alarm.

On that system, a clock_nanosleep(CLOCK_REALTIME_ALARM, ...) results in
"524 Unknown error 524"

Replace it with EOPNOTSUPP which results in the expected "95 Operation not
supported" error.

Fixes: 1c6b39ad3f01 (alarmtimers: Return -ENOTSUPP if no RTC device is present)
Signed-off-by: Thadeu Lima de Souza Cascardo <cascardo@canonical.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Cc: stable@vger.kernel.org
Link: https://lkml.kernel.org/r/20190903171802.28314-1-cascardo@canonical.com
kernel/time/alarmtimer.c