Re: [PATCH 09/13] sched_ext: Make handle_lockup() propagate scx_verror() result

From: Andrea Righi
Date: Mon Nov 10 2025 - 03:30:10 EST


On Sun, Nov 09, 2025 at 08:31:08AM -1000, Tejun Heo wrote:
> handle_lockup() currently calls scx_verror() but ignores its return value,
> always returning true when the scheduler is enabled. Make it capture and return
> the result from scx_verror(). This prepares for hardlockup handling.
>
> Cc: Dan Schatzberg <schatzberg.dan@xxxxxxxxx>
> Cc: Emil Tsalapatis <etsal@xxxxxxxx>
> Signed-off-by: Tejun Heo <tj@xxxxxxxxxx>

Reviewed-by: Andrea Righi <arighi@xxxxxxxxxx>

Thanks,
-Andrea

> ---
> kernel/sched/ext.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/sched/ext.c b/kernel/sched/ext.c
> index 5c75b0125dfe..4507bc4f0b5c 100644
> --- a/kernel/sched/ext.c
> +++ b/kernel/sched/ext.c
> @@ -3658,6 +3658,7 @@ static __printf(1, 2) bool handle_lockup(const char *fmt, ...)
> {
> struct scx_sched *sch;
> va_list args;
> + bool ret;
>
> guard(rcu)();
>
> @@ -3669,9 +3670,9 @@ static __printf(1, 2) bool handle_lockup(const char *fmt, ...)
> case SCX_ENABLING:
> case SCX_ENABLED:
> va_start(args, fmt);
> - scx_verror(sch, fmt, args);
> + ret = scx_verror(sch, fmt, args);
> va_end(args);
> - return true;
> + return ret;
> default:
> return false;
> }
> --
> 2.51.1
>