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]
Date:   Thu, 8 Sep 2022 23:34:07 +0300
From:   Jarkko Sakkinen <jarkko@...nel.org>
To:     Sean Christopherson <seanjc@...gle.com>
Cc:     Harald Hoyer <harald@...fian.com>, ashish.kalra@....com,
        ak@...ux.intel.com, alpergun@...gle.com, ardb@...nel.org,
        bp@...en8.de, dave.hansen@...ux.intel.com, dgilbert@...hat.com,
        dovmurik@...ux.ibm.com, hpa@...or.com, jmattson@...gle.com,
        jroedel@...e.de, kirill@...temov.name, kvm@...r.kernel.org,
        linux-coco@...ts.linux.dev, linux-crypto@...r.kernel.org,
        linux-kernel@...r.kernel.org, linux-mm@...ck.org, luto@...nel.org,
        marcorr@...gle.com, michael.roth@....com, mingo@...hat.com,
        pbonzini@...hat.com, peterz@...radead.org, pgonda@...gle.com,
        rientjes@...gle.com, sathyanarayanan.kuppuswamy@...ux.intel.com,
        slp@...hat.com, srinivas.pandruvada@...ux.intel.com,
        tglx@...utronix.de, thomas.lendacky@....com, tobin@....com,
        tony.luck@...el.com, vbabka@...e.cz, vkuznets@...hat.com,
        x86@...nel.org
Subject: Re: [[PATCH for v6]] KVM: SEV: fix snp_launch_finish

On Thu, Sep 08, 2022 at 03:11:30PM +0000, Sean Christopherson wrote:
> On Thu, Sep 08, 2022, Harald Hoyer wrote:
> > The `params.auth_key_en` indicator does _not_ specify, whether an
> > ID_AUTH struct should be sent or not, but, wheter the ID_AUTH struct
> > contains an author key or not. The firmware always expects an ID_AUTH block.
> > 
> > Link: https://lore.kernel.org/all/cover.1655761627.git.ashish.kalra@amd.com/
> 
> Please provide feedback by directly responding to whatever patch/email is buggy.
> Or if that's too complicated for some reason (unlikely in this case), provide the
> fixup patch to the author *off-list*.

I'd guess that'd be:

https://lore.kernel.org/all/6a513cf79bf71c479dbd72165faf1d804d77b3af.1655761627.git.ashish.kalra@amd.com/

BR, Jarkko

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ