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
| ||
|
Message-ID: <Y4SShb6nMz3gqkwh@zn.tnic> Date: Mon, 28 Nov 2022 11:50:45 +0100 From: Borislav Petkov <bp@...en8.de> To: "Michael Kelley (LINUX)" <mikelley@...rosoft.com> Cc: Sathyanarayanan Kuppuswamy <sathyanarayanan.kuppuswamy@...ux.intel.com>, "hpa@...or.com" <hpa@...or.com>, KY Srinivasan <kys@...rosoft.com>, Haiyang Zhang <haiyangz@...rosoft.com>, "wei.liu@...nel.org" <wei.liu@...nel.org>, Dexuan Cui <decui@...rosoft.com>, "luto@...nel.org" <luto@...nel.org>, "peterz@...radead.org" <peterz@...radead.org>, "davem@...emloft.net" <davem@...emloft.net>, "edumazet@...gle.com" <edumazet@...gle.com>, "kuba@...nel.org" <kuba@...nel.org>, "pabeni@...hat.com" <pabeni@...hat.com>, "lpieralisi@...nel.org" <lpieralisi@...nel.org>, "robh@...nel.org" <robh@...nel.org>, "kw@...ux.com" <kw@...ux.com>, "bhelgaas@...gle.com" <bhelgaas@...gle.com>, "arnd@...db.de" <arnd@...db.de>, "hch@...radead.org" <hch@...radead.org>, "m.szyprowski@...sung.com" <m.szyprowski@...sung.com>, "robin.murphy@....com" <robin.murphy@....com>, "thomas.lendacky@....com" <thomas.lendacky@....com>, "brijesh.singh@....com" <brijesh.singh@....com>, "tglx@...utronix.de" <tglx@...utronix.de>, "mingo@...hat.com" <mingo@...hat.com>, "dave.hansen@...ux.intel.com" <dave.hansen@...ux.intel.com>, Tianyu Lan <Tianyu.Lan@...rosoft.com>, "kirill.shutemov@...ux.intel.com" <kirill.shutemov@...ux.intel.com>, "ak@...ux.intel.com" <ak@...ux.intel.com>, "isaku.yamahata@...el.com" <isaku.yamahata@...el.com>, "Williams, Dan J" <dan.j.williams@...el.com>, "jane.chu@...cle.com" <jane.chu@...cle.com>, "seanjc@...gle.com" <seanjc@...gle.com>, "tony.luck@...el.com" <tony.luck@...el.com>, "x86@...nel.org" <x86@...nel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "linux-hyperv@...r.kernel.org" <linux-hyperv@...r.kernel.org>, "netdev@...r.kernel.org" <netdev@...r.kernel.org>, "linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>, "linux-arch@...r.kernel.org" <linux-arch@...r.kernel.org>, "iommu@...ts.linux.dev" <iommu@...ts.linux.dev> Subject: Re: [Patch v3 05/14] x86/mm: Handle decryption/re-encryption of bss_decrypted consistently On Tue, Nov 22, 2022 at 05:59:04PM +0000, Michael Kelley (LINUX) wrote: > Right. But here's my point: With current code and an image built with > CONFIG_AMD_MEM_ENCRYPT=y and running as a TDX guest, > sme_postprocess_startup() will not decrypt the bss_decrypted section. > Then later mem_encrypt_free_decrypted_mem() will run, see that > CC_ATTR_MEM_ENCRYPT is true, and try to re-encrypt the memory. > In other words, a TDX guest would break in the same way as a Hyper-V > vTOM guest would break. This patch fixes the problem for both cases. I guess making the check more concrete by checking sme_me_mask directly along with a comment makes sense. We need to be very careful here not to fragment the code too much for all the different guest types. -- Regards/Gruss, Boris. https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists