linux-kernel - RE: [PATCH v2 0/8] Decode IA32/X64 CPER

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: <DM5PR12MB1916C801C1340FB36B01DFF4F8A80@DM5PR12MB1916.namprd12.prod.outlook.com>
Date:   Fri, 23 Mar 2018 00:19:20 +0000
From:   "Ghannam, Yazen" <Yazen.Ghannam@....com>
To:     Borislav Petkov <bp@...e.de>
CC:     Tony Luck <tony.luck@...el.com>,
        "linux-efi@...r.kernel.org" <linux-efi@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "ard.biesheuvel@...aro.org" <ard.biesheuvel@...aro.org>,
        "x86@...nel.org" <x86@...nel.org>
Subject: RE: [PATCH v2 0/8] Decode IA32/X64 CPER

> -----Original Message-----
> From: Borislav Petkov <bp@...e.de>
> Sent: Thursday, March 1, 2018 7:00 AM
> To: Ghannam, Yazen <Yazen.Ghannam@....com>
> Cc: Tony Luck <tony.luck@...el.com>; linux-efi@...r.kernel.org; linux-
> kernel@...r.kernel.org; ard.biesheuvel@...aro.org; x86@...nel.org
> Subject: Re: [PATCH v2 0/8] Decode IA32/X64 CPER
> 
> On Wed, Feb 28, 2018 at 08:58:15PM +0000, Ghannam, Yazen wrote:
> > 1) We keep this set mostly as-is. This would be our fallback if we don't have
> > anything better.
> 
> Yes, sounds good. We try to decode it as MCE and if we cannot, we dump
> the raw CPER record.
> 
> > 2) I add the MCA decoding to this set. I was thinking to do this in a separate
> > set but maybe it's better to do it all together.
> 
> I'm fine if you do it separately, as long as you do it so that we have
> user-friendly decoding in the end.
> 

I wanted to add the MCA decoding to this set but I got caught up with something
else and haven't had time to do it.

Is it alright if I go ahead and just send the v3 of this set without the MCA decoding?
I was hoping this could be accepted in the next merge window. And if that's still
possible I'd like to have some CPER decoding sooner rather than nothing.

Thanks,
Yazen