linux-kernel - Re: [PATCH 0/2] Dump stack after certain machine checks

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] [day] [month] [year] [list]

Message-ID: <Y2FZBfCFMSmXduxv@yaz-fattaah>
Date:   Tue, 1 Nov 2022 17:36:05 +0000
From:   Yazen Ghannam <yazen.ghannam@....com>
To:     Borislav Petkov <bp@...en8.de>
Cc:     Tony Luck <tony.luck@...el.com>,
        Smita Koralahalli <Smita.KoralahalliChannabasappa@....com>,
        Carlos Bilbao <carlos.bilbao@....com>, x86@...nel.org,
        linux-edac@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] Dump stack after certain machine checks

On Mon, Oct 31, 2022 at 11:30:03AM +0100, Borislav Petkov wrote:
> On Thu, Sep 22, 2022 at 12:51:34PM -0700, Tony Luck wrote:
> > I've only updated the Intel severity calculation to use this new
> > severity level. I'm not sure if AMD also has situations where this would
> > be useful. If so, then mce_severity_amd() would need to be updated too
> > to return different severity for IN_KERNEL and IN_KERNEL_RECOV cases.
> 
> I'd look into Yazen's direction for that...
>

Yes, I think this is something we can look into. I'm not aware of any
situations at the moment. But I'd like to start focusing more on the various
recovery paths and corner cases.

Thanks,
Yazen