posix-cpu-timers: Sanitize bogus WARNONS
authorThomas Gleixner <tglx@linutronix.de>
Mon, 19 Aug 2019 14:31:46 +0000 (16:31 +0200)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Sat, 5 Oct 2019 11:09:47 +0000 (13:09 +0200)
commit8d5fccff7b0c45b7b0b5e40ac983620eadda0a3b
treefbcf5bfd074ec1ebfa580ee38ae4711323f50fa4
parent9df9652b7345240da92469ff6f794dd52dcb6b34
posix-cpu-timers: Sanitize bogus WARNONS

[ Upstream commit 692117c1f7a6770ed41dd8f277cd9fed1dfb16f1 ]

Warning when p == NULL and then proceeding and dereferencing p does not
make any sense as the kernel will crash with a NULL pointer dereference
right away.

Bailing out when p == NULL and returning an error code does not cure the
underlying problem which caused p to be NULL. Though it might allow to
do proper debugging.

Same applies to the clock id check in set_process_cpu_timer().

Clean them up and make them return without trying to do further damage.

Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Reviewed-by: Frederic Weisbecker <frederic@kernel.org>
Link: https://lkml.kernel.org/r/20190819143801.846497772@linutronix.de
Signed-off-by: Sasha Levin <sashal@kernel.org>
kernel/time/posix-cpu-timers.c