All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josef Bacik <josef@toxicpanda.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: linux-fsdevel@vger.kernel.org,
	Christian Brauner <brauner@kernel.org>,
	Miklos Szeredi <miklos@szeredi.hu>
Subject: Re: [PATCH 0/2] fuse: fix up uid/gid mount option handling
Date: Wed, 3 Jul 2024 10:46:18 -0400	[thread overview]
Message-ID: <20240703144618.GB734942@perftesting> (raw)
In-Reply-To: <89e18d62-3b2d-45db-94f3-41edc4232955@redhat.com>

On Tue, Jul 02, 2024 at 05:12:18PM -0500, Eric Sandeen wrote:
> This short series fixes up fuse uid/gid mount option handling.
> 
> First, as was done for tmpfs in 
> 0200679fc795 ("tmpfs: verify {g,u}id mount options correctly")
> it validates that the requested uid and/or gid is representable in
> the filesystem's idmapping. I've shamelessly copied commit description
> and code from that commit.
> 
> Second, it is switched to use the uid/gid mount helpers proposed at
> https://lore.kernel.org/linux-fsdevel/8dca3c11-99f4-446d-a291-35c50ed2dc14@redhat.com/T/#t
> 
> Both of these are compile-tested only.

Reviewed-by: Josef Bacik <josef@toxicpanda.com>

Thanks,

Josef

  parent reply	other threads:[~2024-07-03 14:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-02 22:12 [PATCH 0/2] fuse: fix up uid/gid mount option handling Eric Sandeen
2024-07-02 22:22 ` [PATCH 1/2] fuse: verify {g,u}id mount options correctly Eric Sandeen
2024-07-02 22:23 ` [PATCH 2/2] fuse: Convert to new uid/gid option parsing helpers Eric Sandeen
2024-07-03 21:26   ` kernel test robot
2024-07-03 21:26   ` kernel test robot
2024-07-04  4:05   ` kernel test robot
2024-07-03  8:38 ` [PATCH 0/2] fuse: fix up uid/gid mount option handling Christian Brauner
2024-07-03 14:46 ` Josef Bacik [this message]
2024-07-03 14:58 ` Christian Brauner

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=20240703144618.GB734942@perftesting \
    --to=josef@toxicpanda.com \
    --cc=brauner@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=sandeen@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.