Received: by 2002:a05:7412:d8a:b0:e2:908c:2ebd with SMTP id b10csp3072373rdg; Tue, 17 Oct 2023 03:58:57 -0700 (PDT) X-Google-Smtp-Source: AGHT+IGIfGw8EH5BikMYfUh75i/M5ulGBwqPs8iLRmqx26/3wBl48AhOlgIssGLyB1jtN71H4e8I X-Received: by 2002:a05:6808:18e:b0:3a4:1c16:b1bc with SMTP id w14-20020a056808018e00b003a41c16b1bcmr2070158oic.12.1697540336884; Tue, 17 Oct 2023 03:58:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1697540336; cv=none; d=google.com; s=arc-20160816; b=OWqvLntVZ52hawVBtPVaK8km4kI9+W7t3DKCl/Dal/trhHWINaqPQ0NeI0ZNrCstyb 4DFgxlLnwbeNcCE2BrXbkL1xuWMeKh5CbM8PhVeVTEou+7PLnD4BI//5Xp0aZ+CYCwGS qlIsIhQAZ0nANp2y4LJpZ2y9fLwDyD2SrGHn4/LkaWuzRtZbIuyu/i6CitUaSKnLR0eW QOT4Fi2Hkv4zoRYpdB1FTieMa+345zzFou6hc8EzzEqnCClhe00RynDWau3T06y70qCR z5c6BA+/WsT93J3n5T+U/moyY1W2f25LHwDqa5lTqA0cJklKR2XL7YTtu6yEu/LGTHxI ELfA== 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=7AvDrSA2O4jubT8nd4WyiQ2wQwwNNb4SRFrLtbdfy5Q=; fh=QJHGcZzQc2+NaR6+J8QkGTp+bI9cceRvmdTYDQLqgH4=; b=m18Pht+fCjfJcZyRWCB4QmnzYR+e6v2BwnCX3JJF3ZbfFsqLVTQ346GuqNNKT+2HJx uR5dqC+sgTbfmledqangNYUGeyY6SbxYPg44hfYCf04ZotleP/0atNtVzKoZdRwd4VAu e95MbxDaZ6Y0Ua+nmNQKs/HxkZF2EVwTxKcvsHPOEL7Wr0Mh3SwNwRtqdZQkWg19LTV7 I23uqKsLpl7zardDJ1hk9hnXGBdrY1YHXbhm3U2cXC3MItA0DlH+YVhzzXGVl0hCdQh4 CHNY+UqcAvRhBFaeh+2N2DRDnL5SAydrgH2Lq49Ut4xtQOT5wMq20iuhx1FaTHGvGZPo wLig== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=MdL7puRn; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:8 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from fry.vger.email (fry.vger.email. [2620:137:e000::3:8]) by mx.google.com with ESMTPS id a71-20020a63904a000000b00589b872029dsi1485278pge.30.2023.10.17.03.58.56 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 17 Oct 2023 03:58:56 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:8 as permitted sender) client-ip=2620:137:e000::3:8; Authentication-Results: mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=MdL7puRn; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:8 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by fry.vger.email (Postfix) with ESMTP id AAAEA802123F; Tue, 17 Oct 2023 03:58:53 -0700 (PDT) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.10 at fry.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234762AbjJQK6i (ORCPT + 99 others); Tue, 17 Oct 2023 06:58:38 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45918 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234599AbjJQK6h (ORCPT ); Tue, 17 Oct 2023 06:58:37 -0400 Received: from mail-vs1-xe35.google.com (mail-vs1-xe35.google.com [IPv6:2607:f8b0:4864:20::e35]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C1FFBA2 for ; Tue, 17 Oct 2023 03:58:34 -0700 (PDT) Received: by mail-vs1-xe35.google.com with SMTP id ada2fe7eead31-457dc26ec2eso942876137.1 for ; Tue, 17 Oct 2023 03:58:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1697540314; x=1698145114; darn=vger.kernel.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=7AvDrSA2O4jubT8nd4WyiQ2wQwwNNb4SRFrLtbdfy5Q=; b=MdL7puRn9ROLAwse884LTdVLAL+MjW3yxUImT9KlS3BraLlfEjaBUbPr2jC551IX0F lgCIshJq7L4rKXdoCKhrnmyuFi7jlUIIrnsHz71i78iA7X+j+I2Emt6FjLsCMmySM5iD zY3GCCMhAkOsGwBdF2tyZYMmT4j7cNdECUeSI49N+UuEy5lQ0tD41DSQIKUc/KjlGJwn 0eH8neYxZzYywYJpQNBJ+3/1QobgVakiIlQFDQc6qWqz3rDBigRdPKibqJ0rZNb9/cmG WfXOjj6ml+tSbOFJjoOPjk9nSDdJWSkFzLLkpQLZWFDwr9gtY5EIsKbqdkDrsvG7uk90 3wcA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1697540314; x=1698145114; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=7AvDrSA2O4jubT8nd4WyiQ2wQwwNNb4SRFrLtbdfy5Q=; b=EmXXQRKR8w7pR6FVvR2ov0S3TZ+riNC20azbKkKM6eP33IB8kC1YVhWqZtApxHWSXh JtixghLn7VwcTq4nOj70vVhq+pZUJsu+Sp9jV+qGyzX1ET8XIgf/q5/oYFoYs+3/FJ1V R+svDNVtP9WvSFcUq8lQbf+Rt6Vl87uxAAPr42oLVLJWi/3rFB3G7FIt+2BDgEqtXc9Y PhAnLK/o1LQbtrEwUlpihkqj+vvkCUNfECaitdQHZi+obxSf+BDFsTThqmZ5kdWc3yzD d8vi1ppaXg5bpKPqAPmijHDJNbVNb7ZEjpA0EmLwCReCnZM/T6vXXVMuEw+0jv9cdX9X MW3w== X-Gm-Message-State: AOJu0YxZe6rFXqzywJ7AkkKgvaGzxf4fIyQEuQea/ImhXv5W8qAhzjXZ 4iVGqdBUT9bgNDHn0fqm9Ob8R6T+irnSVTIoXxyOGA== X-Received: by 2002:a05:6102:54ac:b0:452:c729:e9df with SMTP id bk44-20020a05610254ac00b00452c729e9dfmr2490438vsb.33.1697540313750; Tue, 17 Oct 2023 03:58:33 -0700 (PDT) MIME-Version: 1.0 References: <20230807025343.1939-1-masahisa.kojima@linaro.org> <20230807025343.1939-5-masahisa.kojima@linaro.org> In-Reply-To: From: Sumit Garg Date: Tue, 17 Oct 2023 16:28:22 +0530 Message-ID: Subject: Re: [PATCH v8 4/5] efivarfs: automatically update super block flag To: Ilias Apalodimas Cc: Masahisa Kojima , Ard Biesheuvel , Jens Wiklander , Jan Kiszka , linux-kernel@vger.kernel.org, op-tee@lists.trustedfirmware.org, Johan Hovold , Randy Dunlap , Heinrich Schuchardt , Jonathan Cameron , Jeremy Kerr , linux-efi@vger.kernel.org Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on fry.vger.email Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (fry.vger.email [0.0.0.0]); Tue, 17 Oct 2023 03:58:53 -0700 (PDT) On Fri, 13 Oct 2023 at 20:56, Ilias Apalodimas wrote: > > Hi Sumit > > On Fri, 13 Oct 2023 at 09:53, Sumit Garg wrote: > > > > Hi Ilias, > > > > On Wed, 11 Oct 2023 at 22:30, Ilias Apalodimas > > wrote: > > > > > > Kojima-san > > > Apologies for the late reply, I just found some to test this. > > > > > > On Sun, 6 Aug 2023 at 19:55, Masahisa Kojima wrote: > > > > > > > > efivar operation is updated when the tee_stmm_efi module is probed. > > > > tee_stmm_efi module supports SetVariable runtime service, > > > > but user needs to manually remount the efivarfs as RW to enable > > > > the write access if the previous efivar operation does not support > > > > SerVariable and efivarfs is mounted as read-only. > > > > > > > > This commit notifies the update of efivar operation to > > > > efivarfs subsystem, then drops SB_RDONLY flag if the efivar > > > > operation supports SetVariable. > > > > > > The RO->RW transition works fine and I did manage to test basic stuff > > > like setting up efibootmgr options. IIUC the RW->RO should be covered > > > by this patchset [0] ? > > > > Yeah. > > > > > Wouldn't it be better to detect that the tee device of the supplicant > > > closes and use that to switch the permissions? I get why we need that > > > for the TPM, the entire subsystem needs to send TPM commands *before* > > > the supplicant dies. But this is not needed for the EFI variables > > > case, we could just remount the FS as RO the moment the supplicant > > > dies. > > > > As we discussed offline, we should have a unified approach to notify > > kernel TEE client drivers. So the approach implemented as part of [0] > > should address the needs for fTPM as well as EFI. > > Ideally yes, we should have a unified approach. But this is a bit > different IMHO. In the majority of the cases, the supplicant goes > away, we lose access to storage and that's the only thing we care > about. What do you think about in-flight secure storage operations while the tee-supplicant goes away? They can fail abruptly if the tee-supplicant goes away without waiting for them to complete. IMO, the graceful handling should be that the tee-supplicant should be alive when the dependent devices are being closed. For an EFI variable store case as well isn't that a possible scenario? > Only the TPM subsystem is 'special' because it has to perform > a shutdown of the device as well. On top of that, I think we should > try to avoid the kernel depending on userspace apps as much as > possible. There is only tee-supplicant user-space dependency which has to be handled carefully. I am very much up for RPMB fastpath via kernel and get rid of this dependency as well. > I think it's best if we support both of these and add > documentation on why this is happening. Would it be hard to have a > combination of both of your patches? > It won't be hard but there can be corner cases as mentioned above. -Sumit > Thanks > /Ilias > > > > > -Sumit > > > > > > > > [0] https://lore.kernel.org/all/20230728134832.326467-1-sumit.garg@linaro.org/ > > > > > > Regards > > > /Ilias > > > > > > > > Signed-off-by: Masahisa Kojima > > > > --- > > > > drivers/firmware/efi/efi.c | 6 ++++++ > > > > drivers/firmware/efi/vars.c | 8 ++++++++ > > > > fs/efivarfs/super.c | 33 +++++++++++++++++++++++++++++++++ > > > > include/linux/efi.h | 8 ++++++++ > > > > 4 files changed, 55 insertions(+) > > > > > > > > diff --git a/drivers/firmware/efi/efi.c b/drivers/firmware/efi/efi.c > > > > index 53ae25bbb6ac..d2eec5ed8e5e 100644 > > > > --- a/drivers/firmware/efi/efi.c > > > > +++ b/drivers/firmware/efi/efi.c > > > > @@ -32,6 +32,7 @@ > > > > #include > > > > #include > > > > #include > > > > +#include > > > > > > > > #include > > > > > > > > @@ -187,6 +188,9 @@ static const struct attribute_group efi_subsys_attr_group = { > > > > .is_visible = efi_attr_is_visible, > > > > }; > > > > > > > > +struct blocking_notifier_head efivar_ops_nh; > > > > +EXPORT_SYMBOL_GPL(efivar_ops_nh); > > > > + > > > > static struct efivars generic_efivars; > > > > static struct efivar_operations generic_ops; > > > > > > > > @@ -427,6 +431,8 @@ static int __init efisubsys_init(void) > > > > platform_device_register_simple("efivars", 0, NULL, 0); > > > > } > > > > > > > > + BLOCKING_INIT_NOTIFIER_HEAD(&efivar_ops_nh); > > > > + > > > > error = sysfs_create_group(efi_kobj, &efi_subsys_attr_group); > > > > if (error) { > > > > pr_err("efi: Sysfs attribute export failed with error %d.\n", > > > > diff --git a/drivers/firmware/efi/vars.c b/drivers/firmware/efi/vars.c > > > > index e9dc7116daf1..f654e6f6af87 100644 > > > > --- a/drivers/firmware/efi/vars.c > > > > +++ b/drivers/firmware/efi/vars.c > > > > @@ -63,6 +63,7 @@ int efivars_register(struct efivars *efivars, > > > > const struct efivar_operations *ops) > > > > { > > > > int rv; > > > > + int event; > > > > > > > > if (down_interruptible(&efivars_lock)) > > > > return -EINTR; > > > > @@ -77,6 +78,13 @@ int efivars_register(struct efivars *efivars, > > > > > > > > __efivars = efivars; > > > > > > > > + if (efivar_supports_writes()) > > > > + event = EFIVAR_OPS_RDWR; > > > > + else > > > > + event = EFIVAR_OPS_RDONLY; > > > > + > > > > + blocking_notifier_call_chain(&efivar_ops_nh, event, NULL); > > > > + > > > > pr_info("Registered efivars operations\n"); > > > > rv = 0; > > > > out: > > > > diff --git a/fs/efivarfs/super.c b/fs/efivarfs/super.c > > > > index e028fafa04f3..0f6e4d223aea 100644 > > > > --- a/fs/efivarfs/super.c > > > > +++ b/fs/efivarfs/super.c > > > > @@ -14,11 +14,36 @@ > > > > #include > > > > #include > > > > #include > > > > +#include > > > > > > > > #include "internal.h" > > > > > > > > LIST_HEAD(efivarfs_list); > > > > > > > > +struct efivarfs_info { > > > > + struct super_block *sb; > > > > + struct notifier_block nb; > > > > +}; > > > > + > > > > +static struct efivarfs_info info; > > > > + > > > > +static int efivarfs_ops_notifier(struct notifier_block *nb, unsigned long event, > > > > + void *data) > > > > +{ > > > > + switch (event) { > > > > + case EFIVAR_OPS_RDONLY: > > > > + info.sb->s_flags |= SB_RDONLY; > > > > + break; > > > > + case EFIVAR_OPS_RDWR: > > > > + info.sb->s_flags &= ~SB_RDONLY; > > > > + break; > > > > + default: > > > > + return NOTIFY_DONE; > > > > + } > > > > + > > > > + return NOTIFY_OK; > > > > +} > > > > + > > > > static void efivarfs_evict_inode(struct inode *inode) > > > > { > > > > clear_inode(inode); > > > > @@ -255,6 +280,12 @@ static int efivarfs_fill_super(struct super_block *sb, struct fs_context *fc) > > > > if (!root) > > > > return -ENOMEM; > > > > > > > > + info.sb = sb; > > > > + info.nb.notifier_call = efivarfs_ops_notifier; > > > > + err = blocking_notifier_chain_register(&efivar_ops_nh, &info.nb); > > > > + if (err) > > > > + return err; > > > > + > > > > INIT_LIST_HEAD(&efivarfs_list); > > > > > > > > err = efivar_init(efivarfs_callback, (void *)sb, true, &efivarfs_list); > > > > @@ -281,6 +312,8 @@ static int efivarfs_init_fs_context(struct fs_context *fc) > > > > > > > > static void efivarfs_kill_sb(struct super_block *sb) > > > > { > > > > + blocking_notifier_chain_unregister(&efivar_ops_nh, &info.nb); > > > > + info.sb = NULL; > > > > kill_litter_super(sb); > > > > > > > > if (!efivar_is_available()) > > > > diff --git a/include/linux/efi.h b/include/linux/efi.h > > > > index 603bba2d6437..17cd628b5c42 100644 > > > > --- a/include/linux/efi.h > > > > +++ b/include/linux/efi.h > > > > @@ -1365,6 +1365,14 @@ bool efi_config_table_is_usable(const efi_guid_t *guid, unsigned long table) > > > > > > > > umode_t efi_attr_is_visible(struct kobject *kobj, struct attribute *attr, int n); > > > > > > > > +/* > > > > + * efivar ops event type > > > > + */ > > > > +#define EFIVAR_OPS_RDONLY 0 > > > > +#define EFIVAR_OPS_RDWR 1 > > > > + > > > > +extern struct blocking_notifier_head efivar_ops_nh; > > > > + > > > > void efivars_generic_ops_register(void); > > > > void efivars_generic_ops_unregister(void); > > > > > > > > -- > > > > 2.30.2 > > > >