From: bugzilla-daemon@kernel.org
To: linux-man@vger.kernel.org
Subject: [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: Sat, 10 Oct 2026 18:08:39 +0000 [thread overview]
Message-ID: <bug-222094-11311-xGXc6P7azu@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-222094-11311@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=222094
--- Comment #1 from Alejandro Colomar (alx@kernel.org) ---
Hello,
> Date: 2026-10-05 15:31:25+0000
> From: bugzilla-daemon@kernel.org
>
> https://bugzilla.kernel.org/show_bug.cgi?id=222094
>
[...]
>
> Per https://www.man7.org/linux/man-pages/man2/sched_getattr.2.html:
>
> This scenario documented in the manpage implies that `attr.sched_flags` must
> be
> set to `SCHED_FLAG_RESET_ON_FORK`:
>
> > EINVAL attr.sched_flags contains a flag other than
> > SCHED_FLAG_RESET_ON_FORK.
>
> The second scenario implies that `attr.sched_flags` is a bitmask which can
> contain `SCHED_FLAG_UTIL_CLAMP_MIN` or `SCHED_FLAG_UTIL_CLAMP_MAX`:
>
> > EINVAL attr.sched_flags contains SCHED_FLAG_UTIL_CLAMP_MIN or
> > SCHED_FLAG_UTIL_CLAMP_MAX, and attr.sched_util_min or
> > attr.sched_util_max are out of bounds.
>
> The first case contradicts the second case.
>
> Doing some digging in the kernel source code [1], I couldn't find an obvious
> spot where the first scenario was actually implemented -> **I think the
> `SCHED_FLAG_RESET_ON_FORK ` scenario is a documentation bug.**
>
> 1.
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/kernel/sched/syscalls.c?id=786244f70322e41c937e69f0f935bfd11a9611bf
Would you want to send a patch? If so, please have a look at
<https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/tree/CONTRIBUTIN>.
Have a lovely day!
Alex
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2026-10-10 18:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
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 ` bugzilla-daemon [this message]
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=bug-222094-11311-xGXc6P7azu@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-man@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox