timerqueue: Use rb_entry_safe() in timerqueue_getnext()
authorBarnabás Pőcze <pobrn@protonmail.com>
Mon, 14 Nov 2022 19:54:23 +0000 (19:54 +0000)
committerThomas Gleixner <tglx@linutronix.de>
Thu, 17 Nov 2022 10:26:20 +0000 (11:26 +0100)
commit2f117484329b233455ee278f2d9b0a4356835060
tree2448f4f715047f164f0739d7b5841bcb1f2cf189
parent8be3f96ceddb911539a53d87a66da84a04502366
timerqueue: Use rb_entry_safe() in timerqueue_getnext()

When `timerqueue_getnext()` is called on an empty timer queue, it will
use `rb_entry()` on a NULL pointer, which is invalid. Fix that by using
`rb_entry_safe()` which handles NULL pointers.

This has not caused any issues so far because the offset of the `rb_node`
member in `timerqueue_node` is 0, so `rb_entry()` is essentially a no-op.

Fixes: 511885d7061e ("lib/timerqueue: Rely on rbtree semantics for next timer")
Signed-off-by: Barnabás Pőcze <pobrn@protonmail.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Link: https://lore.kernel.org/r/20221114195421.342929-1-pobrn@protonmail.com
include/linux/timerqueue.h