Hi Enji,

> Date: 2026-10-23 11:58:57-0700
> From: "Enji Cooper (yaneurabeya)" <yaneurabeya@gmail.com>
>
> In more recent versions of the kernel, `.sched_flags` is a treated as a
> bitmask that supports values like `SCHED_FLAG_UTIL_CLAMP_MIN`, etc.
> 
> Account for the additional flags so the documentation is up to date with
> the kernel implementation of `sched_setattr`.
> 
> Ref: linux.git 480a6ca2dc6e ("sched/uclamp: Allow to reset a task uclamp constraint value")
> 
> Signed-off-by: Enji Cooper <yaneurabeya@gmail.com>
> ---
>  man/man2/sched_setattr.2 | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/man/man2/sched_setattr.2 b/man/man2/sched_setattr.2
> index 80a0ac726dcf..64acdd88884f 100644
> --- a/man/man2/sched_setattr.2
> +++ b/man/man2/sched_setattr.2
> @@ -417,7 +417,10 @@ .SH ERRORS
>  .B EINVAL
>  .I attr.sched_flags
>  contains a flag other than
> -.BR SCHED_FLAG_RESET_ON_FORK .
> +.BR SCHED_FLAG_RESET_ON_FORK ,
> +.BR SCHED_FLAG_UTIL_CLAMP_MIN ,
> +or
> +.BR SCHED_FLAG_UTIL_CLAMP_MAX .

Why does this list not include flags such as SCHED_FLAG_RESET_ON_FORK?
It is documented in the same manual page, so I expect it's valid here,
right?


Have a lovely night!
Alex

>  .TP
>  .B EINVAL
>  .I attr.sched_priority
> --  2.50.1 (Apple Git-155)
> 





-- 
<https://www.alejandro-colomar.es>