From: Muchun Song <muchun.song@linux.dev>
To: Giuseppe Scrivano <gscrivan@redhat.com>
Cc: linux-fsdevel@vger.kernel.org,
Christian Brauner <brauner@kernel.org>,
rodrigo@sdfg.com.ar
Subject: Re: [PATCH] hugetlbfs: support idmapped mounts
Date: Fri, 1 Mar 2024 14:45:21 +0800 [thread overview]
Message-ID: <1B974CF9-C919-48F5-AC0F-7F296EC5364F@linux.dev> (raw)
In-Reply-To: <20240229152405.105031-1-gscrivan@redhat.com>
> On Feb 29, 2024, at 23:24, Giuseppe Scrivano <gscrivan@redhat.com> wrote:
>
> pass down the idmapped mount information to the different helper
> functions.
>
> Differently, hugetlb_file_setup() will continue to not have any
> mapping since it is only used from contexts where idmapped mounts are
> not used.
Sorry, could you explain more why you want this changes? What's the
intention?
Thanks.
next prev parent reply other threads:[~2024-03-01 6:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 15:24 [PATCH] hugetlbfs: support idmapped mounts Giuseppe Scrivano
2024-03-01 6:45 ` Muchun Song [this message]
2024-03-01 8:09 ` Giuseppe Scrivano
2024-03-01 8:47 ` Muchun Song
2024-03-01 12:57 ` Christian Brauner
2024-03-04 12:55 ` 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=1B974CF9-C919-48F5-AC0F-7F296EC5364F@linux.dev \
--to=muchun.song@linux.dev \
--cc=brauner@kernel.org \
--cc=gscrivan@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=rodrigo@sdfg.com.ar \
/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).