linux-kernel - Re: [RFC PATCH 00/21] 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]

Message-Id: <20090428113410.e0b04f94.akpm@linux-foundation.org>
Date:	Tue, 28 Apr 2009 11:34:10 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Borislav Petkov <borislav.petkov@....com>
Cc:	greg@...ah.com, linux-kernel@...r.kernel.org,
	Doug Thompson <norsk5@...oo.com>
Subject: Re: [RFC PATCH 00/21] amd64_edac: EDAC module for AMD64


(cc Doug.  He was omitted from the [0/n] email.  Please be careul about
that)

On Tue, 28 Apr 2009 18:06:12 +0200
Borislav Petkov <borislav.petkov@....com> wrote:

> On Tue, Apr 28, 2009 at 08:58:52AM -0700, Greg KH wrote:
> > On Tue, Apr 28, 2009 at 05:05:52PM +0200, Borislav Petkov wrote:
> > > Hi Andrew,
> > > hi Greg,
> > > 
> > > I think you've already heard about this driver, so here is a first
> > > upstream submission request. It is quite sizable but partly the reason
> > > for it is that it handles ECC detection and reporting for all AMD
> > > K8, F10h and F11h families. It also implements DRAM error injection
> > > functionality, failing DIMM module detection and some other fun stuff
> > > found on F10h and later CPUs.
> > > 
> > > We've been doing testing/bugfixing/scrubbing here for some time, have
> > > converted it to using kernel facilities and basically removed some slack
> > > from it like glue code due to it being maintained out-of-tree. Please
> > > take a look and let us know of any objections/comments you might have so
> > > that we could tackle them on time.
> > 
> > At first glance, it looks sane to me.
> > 
> > Want me to put it in my driver tree so it can show up in -next?  Or is
> > there some other tree you want to use?
> 
> -next should be just fine, let the code see some more testing :).

I suspect we will need another iteration because of the rdmsr/wrmsr
thing.

I normally merge EDAC patches via -mm but there will be little overlap
with a new driver such as this and I still haven't got my junk into
linux-next yet.  So whatever.

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