]> git.ipfire.org Git - thirdparty/kernel/linux.git/commit
sched_ext: Fix SCX_EFLAG_INITIALIZED being a no-op flag
authorDavid Carlier <devnexen@gmail.com>
Thu, 26 Feb 2026 12:45:17 +0000 (12:45 +0000)
committerTejun Heo <tj@kernel.org>
Thu, 26 Feb 2026 22:03:24 +0000 (12:03 -1000)
commit749989b2d90ddc7dd253ad3b11a77cf882721acf
tree75393967e79aea7e7e740ad4dc7acdc6f1a33be3
parent2a064262eb378263792cf1fb044de631ac41bcc5
sched_ext: Fix SCX_EFLAG_INITIALIZED being a no-op flag

SCX_EFLAG_INITIALIZED is the sole member of enum scx_exit_flags with no
explicit value, so the compiler assigns it 0. This makes the bitwise OR
in scx_ops_init() a no-op:

    sch->exit_info->flags |= SCX_EFLAG_INITIALIZED; /* |= 0 */

As a result, BPF schedulers cannot distinguish whether ops.init()
completed successfully by inspecting exit_info->flags.

Assign the value 1LLU << 0 so the flag is actually set.

Fixes: f3aec2adce8d ("sched_ext: Add SCX_EFLAG_INITIALIZED to indicate successful ops.init()")
Signed-off-by: David Carlier <devnexen@gmail.com>
Signed-off-by: Tejun Heo <tj@kernel.org>
kernel/sched/ext_internal.h