linux-kernel - Re: [Regression] 2.6.24-git9: RT sched mishandles artswrapper (bisected)

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:	Wed, 06 Feb 2008 23:01:00 +0100
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	Dmitry Adamushko <dmitry.adamushko@...il.com>,
	Ingo Molnar <mingo@...e.hu>,
	Andrew Morton <akpm@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Steven Rostedt <rostedt@...dmis.org>
Subject: Re: [Regression] 2.6.24-git9: RT sched mishandles artswrapper
	(bisected)


On Wed, 2008-02-06 at 22:50 +0100, Rafael J. Wysocki wrote:
> On Wednesday, 6 of February 2008, Peter Zijlstra wrote:

> > Well, that whole queue.
> 
> It doesn't compile for me.

I did solve some compile issues since posting, Ingo should have the
compiling version in sched-devel soonish (don't know if he pushed it
already).

> > Your test program just failed to obtain realtime scheduling
> 
> Well, it shouldn't.  The expected result is to obtain realtime scheduling
> or we will break existing setups.

Thats a case of wrong expectations in my book. You enabled group
scheduling and hence behaviour changes. There is just nothing much one
can do about it, if you don't assign bandwidth to a group, it won't be
able to run anything. Better to refuse to run, than to sit idle, right?

But I appreciate the situation, therefore I made the whole rt-group
scheduling a separate .config option (which defaults to n)

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