From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Jiao Zhou <jiaozhou@google.com>
Cc: Ard Biesheuvel <ardb@kernel.org>, Peter Jones <pjones@redhat.com>,
linux-fsdevel@vger.kernel.org, Jeremy Kerr <jk@ozlabs.org>,
linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kernel: Add Mount Option For Efivarfs
Date: Thu, 24 Aug 2023 18:16:03 +0100 [thread overview]
Message-ID: <ZOeQU9ACbj41g2Ni@srcf.ucam.org> (raw)
In-Reply-To: <CAFyYRf2DschMpD35rkn4-0quKkga=kf0ztQQ3J9ZBvKmKTpAkw@mail.gmail.com>
On Thu, Aug 24, 2023 at 12:51:07PM +0100, Jiao Zhou wrote:
> We want to support fwupd for updating system firmware on Reven. Capsule updates
> need to create UEFI variables. Our current approach to UEFI variables of
> just allowing access to a static list of them at boot time won't work here.
>
> I think we could add mount options to efivarfs to set the uid/gid. We'd
> then mount the file system with fwupd's uid/gid. This approach is used by a
> number of other filesystems that don't have native support for ownership,
> so I think it should be upstreamable.
Makes sense.
Acked-by: Matthew Garrett <mgarrett@aurora.tech>
next prev parent reply other threads:[~2023-08-24 17:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 16:23 [PATCH] kernel: Add Mount Option For Efivarfs Jiao Zhou
2023-08-23 16:30 ` Ard Biesheuvel
2023-08-23 22:30 ` Matthew Garrett
[not found] ` <CAFyYRf2DschMpD35rkn4-0quKkga=kf0ztQQ3J9ZBvKmKTpAkw@mail.gmail.com>
2023-08-24 17:16 ` Matthew Garrett [this message]
2023-08-29 6:24 ` kernel test robot
2023-08-29 7:59 ` Ard Biesheuvel
-- strict thread matches above, loose matches on Subject: below --
2023-08-31 15:31 Jiao Zhou
2023-08-31 15:55 ` Ard Biesheuvel
2023-09-04 12:17 ` Christian Brauner
[not found] ` <CAFyYRf0xyZSLypcHvpzCXQ5dUztTXbE4Ea1xAcQLfbP4+9N9sQ@mail.gmail.com>
2023-09-06 7:06 ` Ard Biesheuvel
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=ZOeQU9ACbj41g2Ni@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=ardb@kernel.org \
--cc=jiaozhou@google.com \
--cc=jk@ozlabs.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pjones@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.