From: joeyli <jlee@suse.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: "Lee, Chun-Yi" <joeyli.kernel@gmail.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
linux-efi <linux-efi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>
Subject: Re: [PATCH] efi/efivars: create efivars mount point when get variable services are available
Date: Mon, 24 Aug 2020 21:03:20 +0800 [thread overview]
Message-ID: <20200824130320.GT7501@linux-l9pv.suse> (raw)
In-Reply-To: <CAMj1kXGx=34tqSWqDUbfJ5WAB-3rWhBc1xsh2-kk2pQgcnfbRQ@mail.gmail.com>
Hi Ard,
On Thu, Aug 20, 2020 at 11:30:27AM +0200, Ard Biesheuvel wrote:
> On Wed, 19 Aug 2020 at 11:28, Lee, Chun-Yi <joeyli.kernel@gmail.com> wrote:
> >
> > The efivars filesystem depends on GetVariable or GetNextVariable EFI
> > runtime services. So the /sys/firmware/efi/efivars does not need to be
> > created when GetVariable and GetNextVariable are not available.
> >
> > It is useful for userland to determine the availability of efivars
> > filesystem.
> >
> > Cc: Ilias Apalodimas <ilias.apalodimas@linaro.org>
> > Cc: Ard Biesheuvel <ardb@kernel.org>
> > Signed-off-by: "Lee, Chun-Yi" <jlee@suse.com>
>
> Hello Joey,
>
> This is not the right check to perform here: the efivarfs code could
> be instantiated using a different efivars abstraction, so whether the
> RT services are implemented is not entirely relevant.
>
> Please look at commit f88814cc2578c121e6edef686365036db72af0ed
> ("efi/efivars: Expose RT service availability via efivars
> abstraction") for an explanation of the underlying issue, and update
> your patch accordingly.
>
Thanks for youre review! I will look at f88814cc257 and change my
patch for v2.
Joey Lee
>
> > ---
> > drivers/firmware/efi/efi.c | 13 ++++++++-----
> > 1 file changed, 8 insertions(+), 5 deletions(-)
> >
> > diff --git a/drivers/firmware/efi/efi.c b/drivers/firmware/efi/efi.c
> > index fdd1db025dbf..929fbf4dfd5d 100644
> > --- a/drivers/firmware/efi/efi.c
> > +++ b/drivers/firmware/efi/efi.c
> > @@ -404,11 +404,14 @@ static int __init efisubsys_init(void)
> > if (error)
> > goto err_remove_group;
> >
> > - /* and the standard mountpoint for efivarfs */
> > - error = sysfs_create_mount_point(efi_kobj, "efivars");
> > - if (error) {
> > - pr_err("efivars: Subsystem registration failed.\n");
> > - goto err_remove_group;
> > + if (efi_rt_services_supported(EFI_RT_SUPPORTED_GET_VARIABLE |
> > + EFI_RT_SUPPORTED_GET_NEXT_VARIABLE_NAME)) {
> > + /* and the standard mountpoint for efivarfs */
> > + error = sysfs_create_mount_point(efi_kobj, "efivars");
> > + if (error) {
> > + pr_err("efivars: Subsystem registration failed.\n");
> > + goto err_remove_group;
> > + }
> > }
> >
> > if (efi_enabled(EFI_DBG) && efi_enabled(EFI_PRESERVE_BS_REGIONS))
> > --
> > 2.16.4
> >
prev parent reply other threads:[~2020-08-24 13:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 9:28 [PATCH] efi/efivars: create efivars mount point when get variable services are available Lee, Chun-Yi
2020-08-20 9:30 ` Ard Biesheuvel
2020-08-24 13:03 ` joeyli [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200824130320.GT7501@linux-l9pv.suse \
--to=jlee@suse.com \
--cc=ard.biesheuvel@linaro.org \
--cc=ardb@kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=joeyli.kernel@gmail.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox