diff options
| author | Zhan Xusheng <zhanxusheng1024@gmail.com> | 2026-04-07 22:36:27 +0800 |
|---|---|---|
| committer | Thomas Gleixner <tglx@kernel.org> | 2026-04-07 19:14:26 +0200 |
| commit | 09c04714cb455debc1dcc3535b6becb52c5b01e0 (patch) | |
| tree | 90661505dce3e5d22210b9ea849b53172c81a290 /tools/perf/scripts/python | |
| parent | c5283a1ffdd5a877120279d164e9d5761e8455af (diff) | |
alarmtimer: Access timerqueue node under lock in suspend
In alarmtimer_suspend(), timerqueue_getnext() is called under
base->lock, but next->expires is read after the lock is released.
This is safe because suspend freezes all relevant task contexts,
but reading the node while holding the lock makes the code easier
to reason about and not worry about a theoretical UAF.
Signed-off-by: Zhan Xusheng <zhanxusheng@xiaomi.com>
Signed-off-by: Thomas Gleixner <tglx@kernel.org>
Link: https://patch.msgid.link/20260407143627.19405-1-zhanxusheng@xiaomi.com
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions