linux-kernel - Re: [PATCH] scheduler: introduce SCHED_RESET_ON

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090605115410.GA16008@elte.hu>
Date:	Fri, 5 Jun 2009 13:54:10 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Lennart Poettering <mzxreary@...inter.de>
Cc:	linux-kernel@...r.kernel.org, peterz@...radead.org
Subject: Re: [PATCH] scheduler: introduce SCHED_RESET_ON_FORK scheduling
	policy flag, Second try


* Lennart Poettering <mzxreary@...inter.de> wrote:

> Why expose this via sched_setscheduler() and not other syscalls 
> such as prctl() or sched_setparam()?
> 
> prctl() does not take a pid parameter. Due to that it would be 
> impossible to modify this flag for other processes than the 
> current one.
> 
> The struct passed to sched_setparam() can unfortunately not be 
> extended without breaking compatibility, since sched_setparam() 
> lacks a size parameter.

Well, it could be extended, if we wanted to. Right now 
sched_priority has a valid value of 0 to 100. We could introduce a 
new value '-1' to mean: 'extended struct sched_param'.

A new getparam syscall could then be introduced - only used by new 
user-space.

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/