linux-kernel - Re: 2.6.32-rc8: amd64

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 01 Dec 2009 09:19:31 -0800
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	Borislav Petkov <borislav.petkov@....com>
CC:	Borislav Petkov <petkovbb@...glemail.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Doug Thompson <dougthompson@...ssion.com>
Subject: Re: 2.6.32-rc8: amd64_edac slub error

Borislav Petkov wrote:
>> EDAC DEBUG: in drivers/edac/amd64_edac.c, line at 2367:     DRAM MEM-CTL PCI Bus ID:	0000:00:18.2
>> EDAC DEBUG: in drivers/edac/amd64_edac.c, line at 2369:     Misc device PCI Bus ID:	0000:00:18.3
>> calling  alsa_pcm_init+0x0/0x71 [snd_pcm] @ 1402
>> initcall alsa_pcm_init+0x0/0x71 [snd_pcm] returned 0 after 17 usecs
>> EDAC amd64: ECC is enabled by BIOS.
>> get_cpus_on_this_dct_cpumask: nid: 0, cpu: 0
>> get_cpus_on_this_dct_cpumask: nid: 0, cpu: 2
>> amd64_nb_mce_bank_enabled_on_node: weight: 2
>> EDAC DEBUG: in drivers/edac/amd64_edac.c, line at 2776: core: 0, MCG_CTL: 0x1f, NB MSR is enabled
>> EDAC DEBUG: in drivers/edac/amd64_edac.c, line at 2776: core: 2, MCG_CTL: 0x0, NB MSR is disabled
>> =============================================================================
>> BUG kmalloc-16: Redzone overwritten
>> -----------------------------------------------------------------------------
> 
> Hmm, I think I know what happens. This machine has non-contigious
> core enumeration on a node (e.g. 0,2 on node 0 instead of 0,1) but
> rdmsr_on_cpus assumes the former. Therefore we write outside of the
> allocated msrs struct and thus the redzone overwrite. Here's a simple
> fix that should take care of it. Please apply on top of the debugging
> patch and catch the output again so that we could verify it.
> 
> I'll fix this properly when I get back and then maybe even backport it
> depending on the intrusiveness of the changes.

Hi,
Here's the new log file (attached).

thanks.
-- 
~Randy

View attachment "edac2.log" of type "text/x-log" (106030 bytes)