From: Hanna Czenczek <hreitz@redhat.com>
To: Josef Bacik <josef@toxicpanda.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-doc@vger.kernel.org, virtualization@lists.linux.dev,
"Miklos Szeredi" <mszeredi@redhat.com>,
"German Maglione" <gmaglione@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Eugenio Pérez" <eperezma@redhat.com>,
"Jonathan Corbet" <corbet@lwn.net>,
"Vivek Goyal" <vgoyal@redhat.com>
Subject: Re: [PATCH 0/2] virtio-fs: Add 'file' mount option
Date: Thu, 11 Jul 2024 16:27:18 +0200 [thread overview]
Message-ID: <151cc130-3584-4b07-96e0-765b7efa43fe@redhat.com> (raw)
In-Reply-To: <453a5eb6-204f-403a-b41d-faefdbcb8f50@redhat.com>
On 11.07.24 10:21, Hanna Czenczek wrote:
> On 10.07.24 20:42, Josef Bacik wrote:
[...]
>> So then the question is, why does it matter what virtiofsd is
>> exposing? I guess
>> that's the better question. The guest shouldn't have to care if it's a
>> directory or a file right? The mountpoint is going to be a
>> directory, whatever
>> is backing it shouldn't matter. Could you describe the exact thing
>> you're
>> trying to accomplish? Thanks,
>
> The mount point needs to be of the same mode as the root node of the
> mounted filesystem, or it’ll be inaccessible after mounting[1]. In
> this case, I want to export a regular file as the root node, so the
> root node must be a regular file, too:
Sorry, I meant “[…], so the mount point must be a regular file, too”.
Hanna
next prev parent reply other threads:[~2024-07-11 14:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-09 11:19 [PATCH 0/2] virtio-fs: Add 'file' mount option Hanna Czenczek
2024-07-09 11:19 ` [PATCH 1/2] " Hanna Czenczek
2024-07-09 11:19 ` [PATCH 2/2] virtio-fs: Document " Hanna Czenczek
2024-07-09 17:56 ` [PATCH 0/2] virtio-fs: Add " Josef Bacik
2024-07-10 7:28 ` Hanna Czenczek
2024-07-10 18:42 ` Josef Bacik
2024-07-11 8:21 ` Hanna Czenczek
2024-07-11 14:27 ` Hanna Czenczek [this message]
2024-07-11 14:34 ` Josef Bacik
2024-07-11 15:04 ` Hanna Czenczek
2024-07-10 17:28 ` Stefan Hajnoczi
2024-07-11 8:31 ` Hanna Czenczek
2024-08-29 8:07 ` Miklos Szeredi
2024-08-29 12:37 ` Hanna Czenczek
2024-08-29 13:07 ` Miklos Szeredi
[not found] ` <b82dd5f9-a214-4a13-b500-38b07f1e9761@redhat.com>
2024-08-29 13:21 ` Miklos Szeredi
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=151cc130-3584-4b07-96e0-765b7efa43fe@redhat.com \
--to=hreitz@redhat.com \
--cc=corbet@lwn.net \
--cc=eperezma@redhat.com \
--cc=gmaglione@redhat.com \
--cc=josef@toxicpanda.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mszeredi@redhat.com \
--cc=stefanha@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).