linux-kernel - RE: [Regression v5.19-rc1] crash kexec fails to boot the 2nd kernel (Re: [PATCH v12 38/46] x86/sev: Add SEV-SNP feature detection/setup)

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:   Wed, 29 Jun 2022 11:06:00 +0000
From:   NOMURA JUNICHI(野村　淳一) 
        <junichi.nomura@....com>
To:     Borislav Petkov <bp@...en8.de>, Michael Roth <michael.roth@....com>
CC:     LKML <linux-kernel@...r.kernel.org>,
        "x86@...nel.org" <x86@...nel.org>
Subject: RE: [Regression v5.19-rc1] crash kexec fails to boot the 2nd kernel
 (Re: [PATCH v12 38/46] x86/sev: Add SEV-SNP feature detection/setup)

From: Borislav Petkov <bp@...en8.de>
> I still think the proper fix is to not execute that cc blob code on
> anything but AMD...

That will solve my case but I'm afraid there may be people with AMD who
hits the same problem.

Isn't it possible for boot loaders to pass cc_blob_address via boot_params?
Information included in struct cc_setup_data is just 'u32 cc_blob_address'
and it seems struct boot_params already has a place reserved for it.

-- 
Jun'ichi Nomura, NEC Corporation / NEC Solution Innovators, Ltd.

Download attachment "smime.p7s" of type "application/pkcs7-signature" (5766 bytes)