linux-kernel - Re: [RFC 0/1][PATCH] POSIX SCHED_SPORADIC implementation for tasks and groups

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]

Date:	Mon, 11 Aug 2008 18:30:52 +0200
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	Dario Faggioli <raistlin@...ux.it>
Cc:	Ulrich Drepper <drepper@...hat.com>, linux-kernel@...r.kernel.org,
	Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>,
	Steven Rostedt <rostedt@...dmis.org>,
	Andrew Morton <akpm@...l.org>
Subject: Re: [RFC 0/1][PATCH] POSIX SCHED_SPORADIC implementation for tasks
	and groups

On Mon, 2008-08-11 at 18:23 +0200, Dario Faggioli wrote:
> On Mon, 2008-08-11 at 16:25 +0200, Peter Zijlstra wrote:
> > My suggestion would be to create struct sched_param2 with plenty of
> > padding to support future expansion and add
> > sys_sched_setscheduler2()/sys_sched_getscheduler2() to deal with this
> > new structure.
> And we will miss POSIX compliance. :-(
> Anyway, I agree the ABI issue this could raise are serious enough and, I
> repeat, I can't see any other solution too.

Well, a new version of glibc could use those to implement the posix
interface. Because as I understand it, glibc can break ABI on certain
version bumps.

--
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/