linux-kernel - Re: [PATCH 2/3] cpumask: fix powernow-k8: partial revert of 2fdf66b491ac706657946442789ec644cc317e1a

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: <86802c440902062359g611b7748n4bbf5e3bbf8023cb@mail.gmail.com>
Date:	Fri, 6 Feb 2009 23:59:27 -0800
From:	Yinghai Lu <yinghai@...nel.org>
To:	Rusty Russell <rusty@...tcorp.com.au>
Cc:	Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org,
	Mike Travis <travis@....com>, "H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH 2/3] cpumask: fix powernow-k8: partial revert of 
	2fdf66b491ac706657946442789ec644cc317e1a

On Fri, Feb 6, 2009 at 11:50 PM, Rusty Russell <rusty@...tcorp.com.au> wrote:
> On Saturday 07 February 2009 18:15:05 Yinghai Lu wrote:
>> Rusty Russell wrote:
>> > 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.
>> >
>>
>> and
>>
>> [PATCH] x86/powernow: dont emit warning when acpi=off
>
> To be clear, is this for 2.6.29, or can wait for .30?
should be .30. just trival...
> The three I sent are needed for 2.6.29 I think.
sure about this one.

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