linux-kernel - Re: possible_cpus broken in linux-next

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] [day] [month] [year] [list]

Message-ID: <8225137.F3AGbHlx43@vostro.rjw.lan>
Date:	Thu, 30 May 2013 00:46:26 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Dave Hansen <dave@...1.net>
Cc:	"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
	Toshi Kani <toshi.kani@...com>,
	Dave Hansen <dave.hansen@...el.com>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	LKML <linux-kernel@...r.kernel.org>, linux-acpi@...r.kernel.org
Subject: Re: possible_cpus broken in linux-next

On Wednesday, May 29, 2013 03:14:12 PM Dave Hansen wrote:
> On 05/29/2013 12:02 PM, Rafael J. Wysocki wrote:
> >>> diff --git a/drivers/base/cpu.c b/drivers/base/cpu.c
> >>> index 130ba0b..b9f0eec 100644
> >>> --- a/drivers/base/cpu.c
> >>> +++ b/drivers/base/cpu.c
> >>> @@ -281,6 +281,7 @@ int __cpuinit register_cpu(struct cpu *cpu, int num)
> >>>       cpu->dev.bus = &cpu_subsys;
> >>>       cpu->dev.release = cpu_device_release;
> >>>       cpu->dev.offline_disabled = !cpu->hotpluggable;
> >>> +    cpu->dev.offline = !cpu_online(num);
> >>>   #ifdef CONFIG_ARCH_HAS_CPU_AUTOPROBE
> >>>       cpu->dev.bus->uevent = arch_cpu_uevent;
> >>>   #endif
> 
> This gets things working for me again.  Thanks for the quick response!
> 
> Tested-by: Dave Hansen <dave.hansen@...el.com>

Applied.

Thanks,
Rafael


-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
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/