linux-kernel - Re: [PATCH] x86/powernow: fix cpus

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: <20090130160431.GA12130@redhat.com>
Date:	Fri, 30 Jan 2009 11:04:31 -0500
From:	Dave Jones <davej@...hat.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Rusty Russell <rusty@...tcorp.com.au>,
	Yinghai Lu <yinghai@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Langsdorf, Mark" <mark.langsdorf@....com>,
	Mike Travis <travis@....com>
Subject: Re: [PATCH] x86/powernow: fix cpus_allowed brokage when acpi=off

On Fri, Jan 30, 2009 at 04:17:01PM +0100, Ingo Molnar wrote:
 > >    Yinghai, as far as I can tell your other fixes are independent (and
 > > were a problem before this commit, yes?).  Can you re-submit them on top
 > > of this patch (which is for Ingo, but against latest Linus).
 > > 
 > > Subject: cpumask: fix powernow-k8: partial revert of 2fdf66b491ac706657946442789ec644cc317e1a
 > > 
 > > Impact: fix powernow-k8 when acpi=off (or other error).
 > > 
 > > There was a spurious change introduced into powernow-k8 in this patch:
 > > the cause if that we try to "restore" the cpus_allowed we never saved.
 > > 
 > > See lkml "[PATCH] x86/powernow: fix cpus_allowed brokage when
 > > acpi=off" from Yinghai for the bug report.
 > > 
 > > Cc: Mike Travis <travis@....com>
 > > Cc: Yinghai Lu <yinghai@...nel.org>
 > > Signed-off-by: Rusty Russell <rusty@...tcorp.com.au>
 > 
 > applied to tip/x86/urgent, thanks guys!
 > 
 > Dave, is it fine if we send the fix to Linus via this route - or would you 
 > like to do it yourself?

I thought this was only in your tree, so I was letting you do the work anyway :-)

I'm fine with it, as long as it goes in soon.

	Dave

-- 
http://www.codemonkey.org.uk
--
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/