linux-kernel - Re: [Patch2/2] fix wrong proc cpuinfo on x64

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]

Date:	Tue, 6 Nov 2007 19:37:10 +0100
From:	"Andreas Herrmann" <andreas.herrmann3@....com>
To:	"Zou Nan hai" <nanhai.zou@...el.com>
cc:	"LKML" <linux-kernel@...r.kernel.org>,
	"Andrew Morton" <akpm@...l.org>
Subject: Re: [Patch2/2] fix wrong proc cpuinfo on x64

On Tue, Nov 06, 2007 at 04:28:20PM +0800, Zou Nan hai wrote:
> in 2.6.24-rc1 kernel, 
> The /proc/cpuinfo display is wrong.
> 
> Another issue is that it will display bogus cpus with wrong information
> if the kernel is compiled with a big CONFIG_NR_CPU.
> 
> That is because before a cpu in cpu_present_map is up, c->cpu_index of
> that cpu is 0.
> thus the cpu_online(c->cpu_index) check in show_cpuinfo is invalid.

This issue should already be fixed with that patch

http://marc.info/?l=linux-kernel&m=119394201230954

> This patch will let cpuinfo_op use cpu_online_map instead of
> cpu_present_map to iterate cpus.

BTW, the problem affects i386 as well.


Regards,

Andreas

-- 
Operating | AMD Saxony Limited Liability Company & Co. KG,
  System  | Wilschdorfer Landstr. 101, 01109 Dresden, Germany
 Research | Register Court Dresden: HRA 4896, General Partner authorized
  Center  | to represent: AMD Saxony LLC (Wilmington, Delaware, US)
  (OSRC)  | General Manager of AMD Saxony LLC: Dr. Hans-R. Deppe, Thomas McCoy



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