diff options
author | Barnabás Pőcze <pobrn@protonmail.com> | 2022-11-14 22:54:23 +0300 |
---|---|---|
committer | Thomas Gleixner <tglx@linutronix.de> | 2022-11-17 13:26:20 +0300 |
commit | 2f117484329b233455ee278f2d9b0a4356835060 (patch) | |
tree | 2448f4f715047f164f0739d7b5841bcb1f2cf189 /Documentation/kernel-hacking/locking.rst | |
parent | 8be3f96ceddb911539a53d87a66da84a04502366 (diff) | |
download | linux-2f117484329b233455ee278f2d9b0a4356835060.tar.xz |
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
Diffstat (limited to 'Documentation/kernel-hacking/locking.rst')
0 files changed, 0 insertions, 0 deletions