All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: Miklos Szeredi <mszeredi@redhat.com>,
	Richard Weinberger <richard.weinberger@gmail.com>,
	David Howells <dhowells@redhat.com>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	virtio-fs@redhat.com, Vivek Goyal <vgoyal@redhat.com>
Subject: Re: [Virtio-fs] [PATCH] init/do_mounts.c: add virtiofs root fs support
Date: Tue, 17 Sep 2019 19:34:25 +0100	[thread overview]
Message-ID: <20190917183425.GJ3370@work-vm> (raw)
In-Reply-To: <20190917183029.GH1131@ZenIV.linux.org.uk>

* Al Viro (viro@zeniv.linux.org.uk) wrote:
> On Tue, Sep 17, 2019 at 08:19:55PM +0200, Richard Weinberger wrote:
> 
> > mtd, ubi, virtiofs and 9p have one thing in common, they are not block devices.
> > What about a new miscroot= kernel parameter?
> 
> How about something like xfs!sda5 or nfs!foo.local.net/bar, etc.?  With
> ubi et.al. covered by the same syntax...

Would Stefan's patch work if there was just a way to test for non-block
based fileystsmes and we replaced
   !strcmp(root_fs_names, "virtiofs") by
   not_block_based_fs(root_fs_names)

Or is there some magic that the other filesystems do that's specific?

Dave

> _______________________________________________
> Virtio-fs mailing list
> Virtio-fs@redhat.com
> https://www.redhat.com/mailman/listinfo/virtio-fs
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK


WARNING: multiple messages have this Message-ID (diff)
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: Richard Weinberger <richard.weinberger@gmail.com>,
	Miklos Szeredi <mszeredi@redhat.com>,
	David Howells <dhowells@redhat.com>,
	virtio-fs@redhat.com,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	Vivek Goyal <vgoyal@redhat.com>
Subject: Re: [Virtio-fs] [PATCH] init/do_mounts.c: add virtiofs root fs support
Date: Tue, 17 Sep 2019 19:34:25 +0100	[thread overview]
Message-ID: <20190917183425.GJ3370@work-vm> (raw)
In-Reply-To: <20190917183029.GH1131@ZenIV.linux.org.uk>

* Al Viro (viro@zeniv.linux.org.uk) wrote:
> On Tue, Sep 17, 2019 at 08:19:55PM +0200, Richard Weinberger wrote:
> 
> > mtd, ubi, virtiofs and 9p have one thing in common, they are not block devices.
> > What about a new miscroot= kernel parameter?
> 
> How about something like xfs!sda5 or nfs!foo.local.net/bar, etc.?  With
> ubi et.al. covered by the same syntax...

Would Stefan's patch work if there was just a way to test for non-block
based fileystsmes and we replaced
   !strcmp(root_fs_names, "virtiofs") by
   not_block_based_fs(root_fs_names)

Or is there some magic that the other filesystems do that's specific?

Dave

> _______________________________________________
> Virtio-fs mailing list
> Virtio-fs@redhat.com
> https://www.redhat.com/mailman/listinfo/virtio-fs
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

  reply	other threads:[~2019-09-17 18:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-06 10:03 [Virtio-fs] [PATCH] init/do_mounts.c: add virtiofs root fs support Stefan Hajnoczi
2019-09-06 10:03 ` Stefan Hajnoczi
2019-09-06 19:16 ` [Virtio-fs] " Richard Weinberger
2019-09-06 19:16   ` Richard Weinberger
2019-09-09  7:00   ` [Virtio-fs] " Stefan Hajnoczi
2019-09-09  7:00     ` Stefan Hajnoczi
2019-09-17 15:18     ` [Virtio-fs] " Stefan Hajnoczi
2019-09-17 15:18       ` Stefan Hajnoczi
2019-09-17 18:19     ` Richard Weinberger
2019-09-17 18:19       ` Richard Weinberger
2019-09-17 18:30       ` [Virtio-fs] " Al Viro
2019-09-17 18:30         ` Al Viro
2019-09-17 18:34         ` Dr. David Alan Gilbert [this message]
2019-09-17 18:34           ` [Virtio-fs] " Dr. David Alan Gilbert
2019-09-18 10:51           ` Stefan Hajnoczi
2019-09-18 10:51             ` Stefan Hajnoczi

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=20190917183425.GJ3370@work-vm \
    --to=dgilbert@redhat.com \
    --cc=dhowells@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=mszeredi@redhat.com \
    --cc=richard.weinberger@gmail.com \
    --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.