linux-kernel - Re: [GIT PULL] EDAC fixes for 3.8

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: <20130311111215.3f12e9ee@redhat.com>
Date:	Mon, 11 Mar 2013 11:12:15 -0300
From:	Mauro Carvalho Chehab <mchehab@...hat.com>
To:	Borislav Petkov <bp@...en8.de>
Cc:	linux-edac <linux-edac@...r.kernel.org>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] EDAC fixes for 3.8

Em Mon, 11 Mar 2013 14:48:14 +0100
Borislav Petkov <bp@...en8.de> escreveu:

> On Mon, Mar 11, 2013 at 09:28:48AM -0300, Mauro Carvalho Chehab wrote:
> > With this patch, mci->csbased field got unused. So, it makes sense to
> > also remove it. The enclosed patch does that.
> 
> AFAIR, this whole fixing was done for K8 as reported by Josh Hunt from
> Akamai: http://marc.info/?l=linux-edac&m=134740440610678 (the whole
> thread contains the discussion).
> 
> So, before we go and change anything in amd64_edac, we need to test
> those on a K8 box. Now, I need ot find one but it would be good if you
> could find one too at RH and test the patches on it before we continue
> with this.

Ok, I'll test it on a K8 box at RH. 

The bug seems to be on K8 rev F, right? Is there a different PCI ID on those
machines? That would help me to quickly find such machine on at RH labs.

Regards,
Mauro
--
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/