[Bug libc/14829] sched_* functions wrongly alter thread scheduling, rather than process

["bugdal at aerifal dot cx" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=14829

--- Comment #8 from Rich Felker <bugdal at aerifal dot cx> ---
No. For at least a couple reasons:

1. SETXID is for a process acting on itself. sched_* can target any PID. Having
glibc accept SETXID signals from other processes would impose some serious
compatibility issues: the sender and receiver would have to have matching ideas
of the protocol. The locking to get it right would also be difficult or
impossible, and there may be permissions issues about sending the signals.

2. Changing the scheduling parameters of a process is not the same thing as
changing the parameters for each thread of the process. Per POSIX, the sched_*
functions are specified to be almost complete NOPs, aside from setting and
retrieving values and checking permissions, etc., on systems that do not
support a process scheduling scope (Linux is such a system). So making them
change all threads would just replace one wrong behavior with another.

-- 
You are receiving this mail because:
You are on the CC list for the bug.