linux-kernel - Re: current linux-2.6.git: cpusets completely broken

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: <alpine.LFD.1.10.0807131136350.2959@woody.linux-foundation.org>
Date:	Sun, 13 Jul 2008 11:38:22 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Ingo Molnar <mingo@...e.hu>
cc:	Dmitry Adamushko <dmitry.adamushko@...il.com>,
	Vegard Nossum <vegard.nossum@...il.com>,
	Paul Menage <menage@...gle.com>,
	Max Krasnyansky <maxk@...lcomm.com>, Paul Jackson <pj@....com>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>, miaox@...fujitsu.com,
	rostedt@...dmis.org, Thomas Gleixner <tglx@...utronix.de>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: current linux-2.6.git: cpusets completely broken



On Sun, 13 Jul 2008, Ingo Molnar wrote:
> 
> mind sending Linus's patch as a completed patchset against tip/master 
> (or tip/sched/devel) so that we can do it in early v2.6.27?

Note that my patch does need lots more eyes and more testing, since it 
needs to make sure that anything that depended on online_map and/or just 
on the scheduling domains now checks active_map instead (or in addition 
to).

> i still think your cpusets.c fix is what we should do for v2.6.26, given 
> that there's agreement about how to fix it for real and thus in terms of 
> regression/bug risk your patch is lower-impact and CPU hotplug has been 
> broken for such a long time.

Agreed. I've pulled it from your tree.

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