[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240904-kehren-umzug-4dbff956b47e@brauner>
Date: Wed, 4 Sep 2024 17:29:16 +0200
From: Christian Brauner <brauner@...nel.org>
To: Miklos Szeredi <miklos@...redi.hu>
Cc: Alexander Mikhalitsyn <aleksandr.mikhalitsyn@...onical.com>,
mszeredi@...hat.com, stgraber@...raber.org, linux-fsdevel@...r.kernel.org,
Seth Forshee <sforshee@...nel.org>, Vivek Goyal <vgoyal@...hat.com>,
German Maglione <gmaglione@...hat.com>, Amir Goldstein <amir73il@...il.com>,
Bernd Schubert <bschubert@....com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 00/15] fuse: basic support for idmapped mounts
On Wed, Sep 04, 2024 at 05:15:40PM GMT, Miklos Szeredi wrote:
> On Tue, 3 Sept 2024 at 17:16, Alexander Mikhalitsyn
> <aleksandr.mikhalitsyn@...onical.com> wrote:
> >
> > Dear friends,
> >
> > This patch series aimed to provide support for idmapped mounts
> > for fuse & virtiofs. We already have idmapped mounts support for almost all
> > widely-used filesystems:
> > * local (ext4, btrfs, xfs, fat, vfat, ntfs3, squashfs, f2fs, erofs, ZFS (out-of-tree))
> > * network (ceph)
>
> Looks good.
>
> Applied with some tweaks and pushed.
Ah, I didn't see your reply. Fwiw, if you agree with my suggestion then
Alex can just put that patch on top of the series or do it after we
landed it. I just think passing NULL 38 times is a bit ugly.
Powered by blists - more mailing lists