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]
Date:   Tue, 18 Jul 2017 16:42:31 +0000
From:   "Kani, Toshimitsu" <toshi.kani@....com>
To:     "rjw@...ysocki.net" <rjw@...ysocki.net>,
        "jhugo@...eaurora.org" <jhugo@...eaurora.org>,
        "bp@...en8.de" <bp@...en8.de>
CC:     "tglx@...utronix.de" <tglx@...utronix.de>,
        "srinivas.pandruvada@...ux.intel.com" 
        <srinivas.pandruvada@...ux.intel.com>,
        "mchehab@...nel.org" <mchehab@...nel.org>,
        "lenb@...nel.org" <lenb@...nel.org>,
        "linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
        "linux-edac@...r.kernel.org" <linux-edac@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 3/3] ghes_edac: add platform check to enable ghes_edac

On Tue, 2017-07-18 at 10:24 -0600, Jeffrey Hugo wrote:
> On 7/18/2017 9:36 AM, Kani, Toshimitsu wrote:
> > On Tue, 2017-07-18 at 08:39 -0600, Jeffrey Hugo wrote:
> > > On 7/17/2017 3:59 PM, Toshi Kani wrote:
> > > > The ghes_edac driver was introduced in 2013 [1], but it has not
> > > > been enabled by any distro yet.
> > > 
> > > Ubuntu is expected to enable this soon.
> > 
> > Interesting.  I was told from other distro that there were many
> > buggy firmwares out there that prevented to enable ghes_edac.  Do
> > you know if Ubuntu has any plan to address such issue?  Or do they
> > not see such issue?  I do not test with other vendors' platforms,
> > so I cannot tell exactly what those bugs are...
> > 
> 
> I do not know if Ubuntu intends to address any "known issues".  I
> know a request was made to Canonical to enable the option, and it
> appears the request is being considered, although the option may be
> limited to ARM64, depending on how Canonical's evaluation goes.  I am
> not aware of any particular issues, so I cannot say what the side
> effects are, or what platforms are considered to exhibit such issues.

I see. Thanks for the info! I hope someone from Canonical is on the
list.
-Toshi

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ