diff options
| author | Pietro Borrello <borrello@diag.uniroma1.it> | 2023-02-06 22:33:54 +0000 |
|---|---|---|
| committer | Peter Zijlstra <peterz@infradead.org> | 2023-02-11 11:18:10 +0100 |
| commit | 7c4a5b89a0b5a57a64b601775b296abf77a9fe97 (patch) | |
| tree | f8dc5bdfda4b3a335fc05b9d6ea4e36ae442455e /arch/alpha | |
| parent | 7ea98dfa44917a201e76d4fe96bf61d76e60f524 (diff) | |
sched/rt: pick_next_rt_entity(): check list_entry
Commit 326587b84078 ("sched: fix goto retry in pick_next_task_rt()")
removed any path which could make pick_next_rt_entity() return NULL.
However, BUG_ON(!rt_se) in _pick_next_task_rt() (the only caller of
pick_next_rt_entity()) still checks the error condition, which can
never happen, since list_entry() never returns NULL.
Remove the BUG_ON check, and instead emit a warning in the only
possible error condition here: the queue being empty which should
never happen.
Fixes: 326587b84078 ("sched: fix goto retry in pick_next_task_rt()")
Signed-off-by: Pietro Borrello <borrello@diag.uniroma1.it>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Reviewed-by: Phil Auld <pauld@redhat.com>
Reviewed-by: Steven Rostedt (Google) <rostedt@goodmis.org>
Link: https://lore.kernel.org/r/20230128-list-entry-null-check-sched-v3-1-b1a71bd1ac6b@diag.uniroma1.it
Diffstat (limited to 'arch/alpha')
0 files changed, 0 insertions, 0 deletions