From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Jiao Zhou <jiaozhou@google.com>, 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: Wed, 23 Aug 2023 23:30:01 +0100 [thread overview]
Message-ID: <ZOaIabhk9a+hyBaI@srcf.ucam.org> (raw)
In-Reply-To: <CAMj1kXHkrRvUbzdNg7WGmBPFW8MtnhEsSy1FOk4GZzVZ1H4fTw@mail.gmail.com>
On Wed, Aug 23, 2023 at 06:30:12PM +0200, Ard Biesheuvel wrote:
> (cc Peter and Matthew)
>
> On Tue, 22 Aug 2023 at 18:24, Jiao Zhou <jiaozhou@google.com> wrote:
> >
> > Add uid and gid in efivarfs's mount option, so that
> > we can mount the file system with ownership. This approach
> > is used by a number of other filesystems that don't have
> > native support for ownership
> >
> > Signed-off-by: Jiao Zhou <jiaozhou@google.com>
No inherent objection, but what's the use case?
next prev parent reply other threads:[~2023-08-23 22:40 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 [this message]
[not found] ` <CAFyYRf2DschMpD35rkn4-0quKkga=kf0ztQQ3J9ZBvKmKTpAkw@mail.gmail.com>
2023-08-24 17:16 ` Matthew Garrett
2023-08-29 6:24 ` kernel test robot
2023-08-29 7:59 ` Ard Biesheuvel
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=ZOaIabhk9a+hyBaI@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).