From: Christian Brauner <brauner@kernel.org>
To: Aleksandr Mikhalitsyn <aleksandr.mikhalitsyn@canonical.com>
Cc: mszeredi@redhat.com, stgraber@stgraber.org,
linux-fsdevel@vger.kernel.org,
Seth Forshee <sforshee@kernel.org>,
Miklos Szeredi <miklos@szeredi.hu>,
Amir Goldstein <amir73il@gmail.com>,
Bernd Schubert <bschubert@ddn.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 9/9] fs/fuse: allow idmapped mounts
Date: Thu, 15 Aug 2024 15:20:07 +0200 [thread overview]
Message-ID: <20240815-duett-verfassen-3ef04efd021f@brauner> (raw)
In-Reply-To: <CAEivzxeQOY6h2AB+eHpnNPAkHMjVoCdOxG99KmkPZx7MVyjhvQ@mail.gmail.com>
> didn't consider setting SB_I_NOIDMAP in fill_super and unsetting it
> later on once
> we had enough information.
No worries, I probably just didn't clarify this.
prev parent reply other threads:[~2024-08-15 13:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 11:40 [PATCH v2 0/9] fuse: basic support for idmapped mounts Alexander Mikhalitsyn
2024-08-14 11:40 ` [PATCH v2 1/9] fs/fuse: add FUSE_OWNER_UID_GID_EXT extension Alexander Mikhalitsyn
2024-08-14 11:40 ` [PATCH v2 2/9] fs/fuse: support idmap for mkdir/mknod/symlink/create Alexander Mikhalitsyn
2024-08-14 11:40 ` [PATCH v2 3/9] fs/fuse: support idmapped getattr inode op Alexander Mikhalitsyn
2024-08-14 11:40 ` [PATCH v2 4/9] fs/fuse: support idmapped ->permission " Alexander Mikhalitsyn
2024-08-14 11:40 ` [PATCH v2 5/9] fs/fuse: support idmapped ->setattr op Alexander Mikhalitsyn
2024-08-14 11:40 ` [PATCH v2 6/9] fs/fuse: drop idmap argument from __fuse_get_acl Alexander Mikhalitsyn
2024-08-14 11:40 ` [PATCH v2 7/9] fs/fuse: support idmapped ->set_acl Alexander Mikhalitsyn
2024-08-14 11:40 ` [PATCH v2 8/9] fs/fuse: properly handle idmapped ->rename op Alexander Mikhalitsyn
2024-08-14 11:40 ` [PATCH v2 9/9] fs/fuse: allow idmapped mounts Alexander Mikhalitsyn
2024-08-14 14:19 ` Christian Brauner
2024-08-15 8:08 ` Aleksandr Mikhalitsyn
2024-08-15 13:20 ` Christian Brauner [this message]
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=20240815-duett-verfassen-3ef04efd021f@brauner \
--to=brauner@kernel.org \
--cc=aleksandr.mikhalitsyn@canonical.com \
--cc=amir73il@gmail.com \
--cc=bschubert@ddn.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 \
/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