linux-kernel - Re: [PATCH] default to n for GROUP_SCHED and FAIR_GROUP

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, 5 May 2008 23:49:04 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Parag Warudkar <parag.warudkar@...il.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	"akpm@...l.org" <akpm@...l.org>,
	Peter Zijlstra <peterz@...radead.org>,
	"H. Peter Anvin" <hpa@...or.com>,
	Arjan van de Ven <arjan@...radead.org>,
	Yinghai Lu <yhlu.kernel@...il.com>,
	Jesse Barnes <jbarnes@...tuousgeek.org>
Subject: Re: [PATCH] default to n for GROUP_SCHED and FAIR_GROUP_SCHED


* Parag Warudkar <parag.warudkar@...il.com> wrote:

> On Mon, May 5, 2008 at 1:21 PM, Ingo Molnar <mingo@...e.hu> wrote:
> 
> >  does -git boot fine - or is this a regression relative to v2.6.25?
> >
> >  I just built your config on latest sched-devel and booted it on two
> >  64-bit testboxes and it boots just fine.
> >
> >  could you send your -git bootup log?
> 
> Hmm - It's the IO_DELAY stuff - I will test more but it looks like 
> with CONFIG_IO_DELAY_TYPE_NONE -git boots fine on my machine but with 
> the same option sched-devel does not. Setting CONFIG_IO_DELAY_TYPE=0 
> (0x80) makes sched-devel boots again.

hm, that's really interesting. I've added a patch that makes 
IO_DELAY_TYPE_NONE depend on CONFIG_BROKEN, because your machine is 
reasonably new but apparently needs delays during bootup. But why 
sched-devel triggered this is still weird.

	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/