Received: by 2002:a05:6a10:9afc:0:0:0:0 with SMTP id t28csp2998276pxm; Mon, 28 Feb 2022 10:01:14 -0800 (PST) X-Google-Smtp-Source: ABdhPJwT3riwkuILJx2fyk6OpbBu6fxoAwor7mjRY9vOH4t1b8/TAFQftdaYFssfK45Hm8KQb+ai X-Received: by 2002:a63:7709:0:b0:36c:8c3c:1199 with SMTP id s9-20020a637709000000b0036c8c3c1199mr18530802pgc.580.1646071274410; Mon, 28 Feb 2022 10:01:14 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1646071274; cv=none; d=google.com; s=arc-20160816; b=GklaQJB3ATVwnnZeyGWGuJBq6hTieDYK+VY9qx8t8geMf3F8wZFcD0RSrTqZ/g83mG PEPfYwcAn5Tzi5tO87c7blWEXdN4479ZtwJEZfUNPiGz+wdtTlAMhWu69S8HbtpKu120 54fCVTd+D0EEMFKgCsV9bnlDKJCGYdk2r74fXgEyV+fv8vGtqhi1iYwHo72ZMd3Wo1Gq OAIF3Tj4bz1NRnCHrWPj+giezoNnRymveX23/PPiYcDXy0IqSewHD2IYshzRZWUphzCh ++4ACvap1/X47fWlSU+YgYegi109+iCo653fbkDgPo3l+fJuiAp7UOG1vKdwn9nDz+9v o7TQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=bkTgMR3x4W5lATfb0ob2zCYpBxmbAAvPoHJJSOP2C+8=; b=R3pRg/FYasox0AwskpamKAE9QTNRc34m83cGsDTBNfSdJ9i1CYhSg3s1PPa8ckmKkk ZL/MEWIa6YVI8fnRUTgTyi2kq3j79sH/XWDDDcll9R8ilPRrV2eMWRY8nzNQJ4Js0ti+ E5Nh53bLR2ujbR4xrx+uJC4JOvu8WAg4t06fx8LLPpkIWXWJUnFy3/KceDNUrj2AhZtE klWDhv0mmfnNfT2RwtQezs/d+BDsppMLTo/buRarHU8brwg7BtjKu3nkXaXWXOVeRJGZ 1+2578wmBKMFl3UMi48UH9ee9gGhEexygOyyIc1OsV4bkGLVOUIVviLgYqWodWXHEQcT 5kiA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=Gc2oLdRh; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id w19-20020a17090a461300b001bca39c52c8si95899pjg.15.2022.02.28.10.00.53; Mon, 28 Feb 2022 10:01:14 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=Gc2oLdRh; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234743AbiB1MuP (ORCPT + 99 others); Mon, 28 Feb 2022 07:50:15 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53276 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231563AbiB1MuM (ORCPT ); Mon, 28 Feb 2022 07:50:12 -0500 Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0863D54FAD; Mon, 28 Feb 2022 04:49:34 -0800 (PST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id 39CA2B81120; Mon, 28 Feb 2022 12:49:32 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id B6F7CC340EE; Mon, 28 Feb 2022 12:49:30 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1646052570; bh=YNCjDWYFLy8kk5Lc6yfDNb4ICpsaXUgkOhGfWYb2mkg=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=Gc2oLdRhB79LqW2fWFa177bVCgVNvknFSspQ4Nx5BBRQEOH9JGJYOzWeIdtF4QlFa Vm6UwbbeLBmvY6Iq2ESWhfaFgokcE1digjq997sEXhVM8APqrUEJvlJLp74Pvk2mC9 yRNCBOSSjomfbtGeQKNyOnmqvTLha8I0x+wfPOqaqZ59Vjpa9evMvPCHvgY/DxynWG py3f1VJxEJwBxXBGz72y7KAMH2QQlJ7pCSCLQBPOevRDSXsr0bSWZpICpprumq0DyN qc9B98cda5m7nLqFZBXESQTvAejiVjGQ+uQ2nokVTcxtk4fkfKfF16U43qXoqK6Aoo G+FEWlvZxX7Vw== Received: by mail-yw1-f180.google.com with SMTP id 00721157ae682-2d07c4a0d06so106264137b3.13; Mon, 28 Feb 2022 04:49:30 -0800 (PST) X-Gm-Message-State: AOAM530pRLkjn3F9zF8Me5GJnEZPnwIjsZ6crvXmh3vjAHvygJcnU8iL l6ZX4Ahb4Tu+jgrAPxZUXCe13I7yS1aoIahGOEY= X-Received: by 2002:a81:854:0:b0:2db:255b:dd6 with SMTP id 81-20020a810854000000b002db255b0dd6mr13412601ywi.140.1646052569778; Mon, 28 Feb 2022 04:49:29 -0800 (PST) MIME-Version: 1.0 References: <20220228114254.1099945-1-dovmurik@linux.ibm.com> <20220228114254.1099945-4-dovmurik@linux.ibm.com> In-Reply-To: <20220228114254.1099945-4-dovmurik@linux.ibm.com> From: Ard Biesheuvel Date: Mon, 28 Feb 2022 13:49:19 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v8 3/4] efi: Load efi_secret module if EFI secret area is populated To: Dov Murik Cc: linux-efi , Gerd Hoffmann , Borislav Petkov , Ashish Kalra , Brijesh Singh , Tom Lendacky , James Morris , "Serge E. Hallyn" , Andi Kleen , Greg KH , Andrew Scull , Dave Hansen , "Dr. David Alan Gilbert" , Lenny Szubowicz , Peter Gonda , Matthew Garrett , James Bottomley , Tobin Feldman-Fitzthum , Jim Cadden , Daniele Buono , linux-coco@lists.linux.dev, linux-security-module@vger.kernel.org, Linux Kernel Mailing List Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-7.5 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 28 Feb 2022 at 12:43, Dov Murik wrote: > > If the efi_secret module is built, register a late_initcall in the EFI > driver which checks whether the EFI secret area is available and > populated, and then requests to load the efi_secret module. > > This will cause the /secrets/coco directory to appear in > guests into which secrets were injected; in other cases, the module is > not loaded. > > Signed-off-by: Dov Murik > Reviewed-by: Gerd Hoffmann It would be better to simply expose a platform device and associated driver, instead of hooking into the module machinery directly. We already do something similar for the EFI rtc and the efivars subsystem, using platform_device_register_simple() > --- > drivers/firmware/efi/Makefile | 1 + > drivers/firmware/efi/coco.c | 58 ++++++++++++++++++++ > drivers/virt/coco/efi_secret/Kconfig | 3 + > 3 files changed, 62 insertions(+) > > diff --git a/drivers/firmware/efi/Makefile b/drivers/firmware/efi/Makefile > index c02ff25dd477..49c4a8c0bfc4 100644 > --- a/drivers/firmware/efi/Makefile > +++ b/drivers/firmware/efi/Makefile > @@ -32,6 +32,7 @@ obj-$(CONFIG_APPLE_PROPERTIES) += apple-properties.o > obj-$(CONFIG_EFI_RCI2_TABLE) += rci2-table.o > obj-$(CONFIG_EFI_EMBEDDED_FIRMWARE) += embedded-firmware.o > obj-$(CONFIG_LOAD_UEFI_KEYS) += mokvar-table.o > +obj-$(CONFIG_EFI_COCO_SECRET) += coco.o > > fake_map-y += fake_mem.o > fake_map-$(CONFIG_X86) += x86_fake_mem.o > diff --git a/drivers/firmware/efi/coco.c b/drivers/firmware/efi/coco.c > new file mode 100644 > index 000000000000..f8efd240ab05 > --- /dev/null > +++ b/drivers/firmware/efi/coco.c > @@ -0,0 +1,58 @@ > +// SPDX-License-Identifier: GPL-2.0 > +/* > + * Confidential computing (coco) secret area handling > + * > + * Copyright (C) 2021 IBM Corporation > + * Author: Dov Murik > + */ > + > +#define pr_fmt(fmt) "efi: " fmt > + > +#include > +#include > +#include > +#include > + > +#ifdef CONFIG_EFI_SECRET_MODULE > + > +/* > + * Load the efi_secret module if the EFI secret area is populated > + */ > +static int __init load_efi_secret_module(void) > +{ > + struct linux_efi_coco_secret_area *area; > + efi_guid_t *header_guid; > + int ret = 0; > + > + if (efi.coco_secret == EFI_INVALID_TABLE_ADDR) > + return 0; > + > + area = memremap(efi.coco_secret, sizeof(*area), MEMREMAP_WB); > + if (!area) { > + pr_err("Failed to map confidential computing secret area descriptor\n"); > + return -ENOMEM; > + } > + if (!area->base_pa || area->size < sizeof(*header_guid)) > + goto unmap_desc; > + > + header_guid = (void __force *)ioremap_encrypted(area->base_pa, sizeof(*header_guid)); > + if (!header_guid) { > + pr_err("Failed to map secret area\n"); > + ret = -ENOMEM; > + goto unmap_desc; > + } > + if (efi_guidcmp(*header_guid, EFI_SECRET_TABLE_HEADER_GUID)) > + goto unmap_encrypted; > + > + ret = request_module("efi_secret"); > + > +unmap_encrypted: > + iounmap((void __iomem *)header_guid); > + > +unmap_desc: > + memunmap(area); > + return ret; > +} > +late_initcall(load_efi_secret_module); > + > +#endif > diff --git a/drivers/virt/coco/efi_secret/Kconfig b/drivers/virt/coco/efi_secret/Kconfig > index 4404d198f3b2..dc8da2921e36 100644 > --- a/drivers/virt/coco/efi_secret/Kconfig > +++ b/drivers/virt/coco/efi_secret/Kconfig > @@ -14,3 +14,6 @@ config EFI_SECRET > > To compile this driver as a module, choose M here. > The module will be called efi_secret. > + > + The module is loaded automatically by the EFI driver if the EFI > + secret area is populated. > -- > 2.25.1 >