From: Alejandro Colomar <alx@kernel.org>
To: linux-man@vger.kernel.org
Cc: Enji Cooper <yaneurabeya@gmail.com>
Subject: Re: [Bug 222094] sched_setattr: bug in `ERRORS` section w.r.t. `attr.sched_flags contains a flag other than SCHED_FLAG_RESET_ON_FORK`
Date: Fri, 23 Oct 2026 21:31:17 +0200 [thread overview]
Message-ID: <atu2BZy0EYMaoTk-@debian> (raw)
In-Reply-To: <atu07uXukn8V_4YN@debian>
[-- Attachment #1: Type: text/plain, Size: 2766 bytes --]
[moving discussion to the mailing list]
Hi Enji,
> Date: 2026-10-23 21:27:52+0200
> From: Alejandro Colomar <alx@kernel.org>
>
> Hi,
>
> > Date: 2026-10-23 18:47:22+0000
> > From: bugzilla-daemon@kernel.org
> >
> > https://bugzilla.kernel.org/show_bug.cgi?id=222094
> >
> > --- Comment #2 from Enji Cooper (yaneurabeya@gmail.com) ---
> > Created attachment 311258
> > --> https://bugzilla.kernel.org/attachment.cgi?id=311258&action=edit
> > Patch
> >
> > I've honestly never submitted a patch to the Linux mailing lists. There are a
> > lot of hoops to jump through in order to make a contribution... I'll try, but
> > please bear with me (I'll probably get something wrong).
>
> Sure! You're welcome to try. :-)
>
> I've forwarded your patch to the mailing list in this email.
>
>
> Have a lovely night!
> Alex
>
> --
> <https://www.alejandro-colomar.es>
> From cfaef3da82a115fbce47dec58b458c6cfc439667 Mon Sep 17 00:00:00 2001
> Message-ID: <cfaef3da82a115fbce47dec58b458c6cfc439667.1792780609.git.yaneurabeya@gmail.com>
> From: Enji Cooper <yaneurabeya@gmail.com>
> Date: Fri, 23 Oct 2026 10:39:20 -0700
> Subject: [PATCH] man/man2/sched_setattr.2: update `EINVAL` case with
> `.sched_flags`
> To: Alejandro Colomar <alx+linux-man@kernel.org>
> Cc: <linux-man@vger.kernel.org>
>
> 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 | 13 ++++++++-----
> 1 file changed, 8 insertions(+), 5 deletions(-)
>
> diff --git a/man/man2/sched_setattr.2 b/man/man2/sched_setattr.2
> index 80a0ac726dcf..b163ba482390 100644
> --- a/man/man2/sched_setattr.2
> +++ b/man/man2/sched_setattr.2
> @@ -411,13 +411,16 @@ .SH ERRORS
> .BR sched (7).
> .TP
> .B EINVAL
> -.I attr.sched_policy
> -is not one of the recognized policies.
> -.TP
> -.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 .
> +.TP
> +.B EINVAL
> +.I attr.sched_policy
> +is not one of the recognized policies.
I wonder why you moved this paragraph. It doesn't seem to be necessary,
right?
Cheers,
Alex
> .TP
> .B EINVAL
> .I attr.sched_priority
> --
> 2.50.1 (Apple Git-155)
>
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next parent reply other threads:[~2026-10-23 19:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-222094-216477@https.bugzilla.kernel.org/>
[not found] ` <bug-222094-216477-AkltlLpJO7@https.bugzilla.kernel.org/>
[not found] ` <atu07uXukn8V_4YN@debian>
2026-10-23 19:31 ` Alejandro Colomar [this message]
2026-10-05 15:31 [Bug 222094] New: sched_setattr: bug in `ERRORS` section w.r.t. `attr.sched_flags contains a flag other than SCHED_FLAG_RESET_ON_FORK` bugzilla-daemon
2026-10-10 18:08 ` [Bug 222094] " bugzilla-daemon
2026-10-23 18:47 ` bugzilla-daemon
2026-10-23 19:27 ` bugzilla-daemon
2026-10-23 19:27 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=atu2BZy0EYMaoTk-@debian \
--to=alx@kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=yaneurabeya@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.