From: Stefan Hajnoczi <stefanha@redhat.com>
To: Alexander Mikhalitsyn <aleksandr.mikhalitsyn@canonical.com>
Cc: mszeredi@redhat.com, brauner@kernel.org, stgraber@stgraber.org,
linux-fsdevel@vger.kernel.org,
"Seth Forshee" <sforshee@kernel.org>,
"Miklos Szeredi" <miklos@szeredi.hu>,
"Vivek Goyal" <vgoyal@redhat.com>,
"German Maglione" <gmaglione@redhat.com>,
"Amir Goldstein" <amir73il@gmail.com>,
"Bernd Schubert" <bschubert@ddn.com>,
"Eugenio Pérez" <eperezma@redhat.com>,
linux-kernel@vger.kernel.org, virtualization@lists.linux.dev
Subject: Re: [PATCH v4 15/15] fs/fuse/virtio_fs: allow idmapped mounts
Date: Thu, 5 Sep 2024 15:45:26 -0400 [thread overview]
Message-ID: <20240905194526.GK1922502@fedora> (raw)
In-Reply-To: <20240903151626.264609-16-aleksandr.mikhalitsyn@canonical.com>
[-- Attachment #1: Type: text/plain, Size: 1020 bytes --]
On Tue, Sep 03, 2024 at 05:16:26PM +0200, Alexander Mikhalitsyn wrote:
> Allow idmapped mounts for virtiofs.
> It's absolutely safe as for virtiofs we have the same
> feature negotiation mechanism as for classical fuse
> filesystems. This does not affect any existing
> setups anyhow.
>
> virtiofsd support:
> https://gitlab.com/virtio-fs/virtiofsd/-/merge_requests/245
>
> Cc: Christian Brauner <brauner@kernel.org>
> Cc: Seth Forshee <sforshee@kernel.org>
> Cc: Miklos Szeredi <miklos@szeredi.hu>
> Cc: Vivek Goyal <vgoyal@redhat.com>
> Cc: German Maglione <gmaglione@redhat.com>
> Cc: Amir Goldstein <amir73il@gmail.com>
> Cc: Bernd Schubert <bschubert@ddn.com>
> Cc: <linux-fsdevel@vger.kernel.org>
> Signed-off-by: Alexander Mikhalitsyn <aleksandr.mikhalitsyn@canonical.com>
> Reviewed-by: Christian Brauner <brauner@kernel.org>
> ---
> v3:
> - this commit added
> ---
> fs/fuse/virtio_fs.c | 1 +
> 1 file changed, 1 insertion(+)
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-09-05 19:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 15:16 [PATCH v4 00/15] fuse: basic support for idmapped mounts Alexander Mikhalitsyn
2024-09-03 15:16 ` [PATCH v4 01/15] fs/namespace: introduce SB_I_NOIDMAP flag Alexander Mikhalitsyn
2024-09-03 15:16 ` [PATCH v4 02/15] fs/fuse: add basic infrastructure to support idmappings Alexander Mikhalitsyn
2024-09-03 15:16 ` [PATCH v4 03/15] fs/fuse: add an idmap argument to fuse_simple_request Alexander Mikhalitsyn
2024-09-04 15:25 ` Christian Brauner
2024-09-03 15:16 ` [PATCH v4 04/15] fs/fuse: support idmapped FUSE_EXT_GROUPS Alexander Mikhalitsyn
2024-09-03 15:16 ` [PATCH v4 05/15] fs/fuse: support idmap for mkdir/mknod/symlink/create/tmpfile Alexander Mikhalitsyn
2024-09-03 15:16 ` [PATCH v4 06/15] fs/fuse: support idmapped getattr inode op Alexander Mikhalitsyn
2024-09-03 15:16 ` [PATCH v4 07/15] fs/fuse: support idmapped ->permission " Alexander Mikhalitsyn
2024-09-03 15:16 ` [PATCH v4 08/15] fs/fuse: support idmapped ->setattr op Alexander Mikhalitsyn
2024-09-03 15:16 ` [PATCH v4 09/15] fs/fuse: drop idmap argument from __fuse_get_acl Alexander Mikhalitsyn
2024-09-03 15:16 ` [PATCH v4 10/15] fs/fuse: support idmapped ->set_acl Alexander Mikhalitsyn
2024-09-03 15:16 ` [PATCH v4 11/15] fs/fuse: support idmapped ->rename op Alexander Mikhalitsyn
2024-09-03 15:16 ` [PATCH v4 12/15] fs/fuse: handle idmappings properly in ->write_iter Alexander Mikhalitsyn
2024-09-03 15:16 ` [PATCH v4 13/15] fs/fuse: warn if fuse_access is called when idmapped mounts are allowed Alexander Mikhalitsyn
2024-09-03 15:16 ` [PATCH v4 14/15] fs/fuse: allow idmapped mounts Alexander Mikhalitsyn
2024-09-03 15:16 ` [PATCH v4 15/15] fs/fuse/virtio_fs: " Alexander Mikhalitsyn
2024-09-05 19:45 ` Stefan Hajnoczi [this message]
2024-09-04 15:15 ` [PATCH v4 00/15] fuse: basic support for " Miklos Szeredi
2024-09-04 15:29 ` Christian Brauner
2024-09-04 16:59 ` Miklos Szeredi
2024-09-04 17:21 ` Aleksandr Mikhalitsyn
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=20240905194526.GK1922502@fedora \
--to=stefanha@redhat.com \
--cc=aleksandr.mikhalitsyn@canonical.com \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=bschubert@ddn.com \
--cc=eperezma@redhat.com \
--cc=gmaglione@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=mszeredi@redhat.com \
--cc=sforshee@kernel.org \
--cc=stgraber@stgraber.org \
--cc=vgoyal@redhat.com \
--cc=virtualization@lists.linux.dev \
/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