From: Dominique Martinet <asmadeus@codewreck.org>
To: Vivek Goyal <vgoyal@redhat.com>, Changbin Du <changbin.du@gmail.com>
Cc: David Howells <dhowells@redhat.com>,
Miklos Szeredi <miklos@szeredi.hu>,
Richard Weinberger <richard.weinberger@gmail.com>,
linux kernel mailing list <linux-kernel@vger.kernel.org>,
virtio-fs@redhat.com, Enrico Weigelt <lkml@metux.net>,
viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org,
v9fs-developer@lists.sourceforge.net
Subject: Re: [Virtio-fs] [PATCH] init/do_mounts.c: Add root="fstag:<tag>" syntax for root device
Date: Wed, 9 Jun 2021 06:41:38 +0900 [thread overview]
Message-ID: <YL/kEpcaYE/Jr0J7@codewreck.org> (raw)
In-Reply-To: <20210608153524.GB504497@redhat.com>
... And that's why I told Changbin Du a few times his patches needed
more Ccs :/
FWIW: we just got last month a couple of patches that would allow
initrd-less 9p root mount (using the nfs/cifs method described below
with root=/dev/v9fs)
Vivek Goyal wrote on Tue, Jun 08, 2021 at 11:35:24AM -0400:
> NFS and CIFS use "root=/dev/nfs" and CIFS passes "root=/dev/cifs" and
> actual root device details come from filesystem specific kernel
> command line options.
>
> virtiofs does not seem to fit in any of the above categories. In fact
> we have 9pfs which can be used to boot from but it also does not
> have a proper syntax to specify rootfs and does not fit into any of
> the existing syntax. They both expect a device "tag" to be passed
> in a device to be mounted. And filesystem knows how to parse and
> use "tag".
>
> So this patch proposes that we add a new prefix "fstag:" which specifies
> that identifier which follows is filesystem specific tag and its not
> a block device. Just pass this tag to filesystem and filesystem will
> figure out how to mount it.
...However I agree something more generic would be welcome in my
opinion, so I like this approach.
I'll give it a try for 9p over the weekend and report back.
--
Dominique
WARNING: multiple messages have this Message-ID (diff)
From: Dominique Martinet <asmadeus@codewreck.org>
To: Vivek Goyal <vgoyal@redhat.com>, Changbin Du <changbin.du@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, virtio-fs@redhat.com,
linux kernel mailing list <linux-kernel@vger.kernel.org>,
Miklos Szeredi <miklos@szeredi.hu>,
David Howells <dhowells@redhat.com>,
viro@zeniv.linux.org.uk, stefanha@redhat.com,
Richard Weinberger <richard.weinberger@gmail.com>,
dgilbert@redhat.com, v9fs-developer@lists.sourceforge.net,
Enrico Weigelt <lkml@metux.net>
Subject: Re: [PATCH] init/do_mounts.c: Add root="fstag:<tag>" syntax for root device
Date: Wed, 9 Jun 2021 06:41:38 +0900 [thread overview]
Message-ID: <YL/kEpcaYE/Jr0J7@codewreck.org> (raw)
In-Reply-To: <20210608153524.GB504497@redhat.com>
... And that's why I told Changbin Du a few times his patches needed
more Ccs :/
FWIW: we just got last month a couple of patches that would allow
initrd-less 9p root mount (using the nfs/cifs method described below
with root=/dev/v9fs)
Vivek Goyal wrote on Tue, Jun 08, 2021 at 11:35:24AM -0400:
> NFS and CIFS use "root=/dev/nfs" and CIFS passes "root=/dev/cifs" and
> actual root device details come from filesystem specific kernel
> command line options.
>
> virtiofs does not seem to fit in any of the above categories. In fact
> we have 9pfs which can be used to boot from but it also does not
> have a proper syntax to specify rootfs and does not fit into any of
> the existing syntax. They both expect a device "tag" to be passed
> in a device to be mounted. And filesystem knows how to parse and
> use "tag".
>
> So this patch proposes that we add a new prefix "fstag:" which specifies
> that identifier which follows is filesystem specific tag and its not
> a block device. Just pass this tag to filesystem and filesystem will
> figure out how to mount it.
...However I agree something more generic would be welcome in my
opinion, so I like this approach.
I'll give it a try for 9p over the weekend and report back.
--
Dominique
next prev parent reply other threads:[~2021-06-08 21:41 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 15:35 [Virtio-fs] [PATCH] init/do_mounts.c: Add root="fstag:<tag>" syntax for root device Vivek Goyal
2021-06-08 15:35 ` Vivek Goyal
2021-06-08 18:38 ` [Virtio-fs] " Harry G. Coin
2021-06-08 19:26 ` Vivek Goyal
2021-06-08 19:26 ` Vivek Goyal
2021-06-08 19:49 ` Harry G. Coin
2021-06-08 19:49 ` Harry G. Coin
2021-06-08 21:41 ` Dominique Martinet [this message]
2021-06-08 21:41 ` Dominique Martinet
2021-06-09 9:51 ` [Virtio-fs] " Stefan Hajnoczi
2021-06-09 9:51 ` Stefan Hajnoczi
2021-06-09 14:13 ` [Virtio-fs] " Harry G. Coin
2021-06-09 14:13 ` Harry G. Coin
2021-06-09 15:45 ` Vivek Goyal
2021-06-09 15:45 ` Vivek Goyal
2021-06-10 8:16 ` [Virtio-fs] " Stefan Hajnoczi
2021-06-10 8:16 ` Stefan Hajnoczi
2021-06-10 8:33 ` [Virtio-fs] " Dominique Martinet
2021-06-10 8:33 ` Dominique Martinet
2021-06-13 11:56 ` [Virtio-fs] " Dominique Martinet
2021-06-13 11:56 ` Dominique Martinet
2021-06-14 14:28 ` [Virtio-fs] " Vivek Goyal
2021-06-14 14:28 ` Vivek Goyal
2021-06-14 23:14 ` [Virtio-fs] " Dominique Martinet
2021-06-14 23:14 ` Dominique Martinet
2021-06-15 13:50 ` [Virtio-fs] " Vivek Goyal
2021-06-15 13:50 ` Vivek Goyal
2021-06-16 3:24 ` [Virtio-fs] " Dominique Martinet
2021-06-16 3:24 ` Dominique Martinet
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=YL/kEpcaYE/Jr0J7@codewreck.org \
--to=asmadeus@codewreck.org \
--cc=changbin.du@gmail.com \
--cc=dhowells@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@metux.net \
--cc=miklos@szeredi.hu \
--cc=richard.weinberger@gmail.com \
--cc=v9fs-developer@lists.sourceforge.net \
--cc=vgoyal@redhat.com \
--cc=viro@zeniv.linux.org.uk \
--cc=virtio-fs@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.