From: Wouter Verhelst <w@uter.be>
To: Markus Pargmann <mpa@pengutronix.de>
Cc: nbd-general@lists.sourceforge.net,
Paul Clements <Paul.Clements@steeleye.com>,
linux-kernel@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [Nbd] [RFC 4/4] nbd: Add support for nbd as root device
Date: Fri, 30 Jan 2015 18:30:14 +0100 [thread overview]
Message-ID: <20150130173014.GA16754@grep.be> (raw)
In-Reply-To: <20150130080400.GD16879@pengutronix.de>
On Fri, Jan 30, 2015 at 09:04:00AM +0100, Markus Pargmann wrote:
> Hi,
>
> On Fri, Jan 30, 2015 at 12:42:54AM +0100, Wouter Verhelst wrote:
> > Not that I'm opposed to this, but you do realize that doing nbd-client
> > from initramfs or similar is possible, right? Most initramfs
> > implementations these days support it.
>
> Yes, that was the first idea how to implement a complete netboot for an
> embedded ARM device. However, an initramfs is at least around 1MB in
> size which has to be loaded using tftp. As the essential nbd-client
> connection setup and negotiation is quite small I decided to go with
> nbd-root support.
>
> Also it is quite useful to have nbd-root support much like nfsroot
> directly built-in for debugging purposes. It has the big advantage of
> booting/testing read-only filesystem images for embedded systems without
> the need for an initramfs.
Fair enough, just thought I'd point it out.
When looking at your patch set, two things pop out which you should
probably look at:
- What will happen if someone boots with root-on-NBD in your scheme and
later does a pivot_root() followed by an NBD_DISCONNECT ioctl on the
device?
- When a connection is started by nbd-client, the kernel creates a "pid"
file in sysfs, which contains the PID of the client and which the
client (when called with -c, or in other cases) uses to verify whether
a device is connected. At first glance, your patch does not do this,
which could cause confusion.
I must admit I haven't checked your patch very well (my kernel fu isn't
that advanced) so I might have missed something, but I'd rather point
it out now than have to fix the pieces afterwards ;-)
--
It is easy to love a country that is famous for chocolate and beer
-- Barack Obama, speaking in Brussels, Belgium, 2014-03-26
next prev parent reply other threads:[~2015-01-30 17:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 13:44 [RFC 0/4] nbd: root device support Markus Pargmann
2015-01-13 13:44 ` [RFC 1/4] nbd: Replace kthread_create with kthread_run Markus Pargmann
2015-01-13 13:44 ` [RFC 2/4] nbd: Split 'DO_IT' into three functions Markus Pargmann
2015-01-26 16:16 ` Paul Clements
2015-01-26 16:23 ` Markus Pargmann
2015-01-13 13:44 ` [RFC 3/4] nbd: Create helper functions for ioctls Markus Pargmann
2015-01-28 21:04 ` Paul Clements
2015-01-30 7:54 ` Markus Pargmann
2015-01-13 13:44 ` [RFC 4/4] nbd: Add support for nbd as root device Markus Pargmann
2015-01-20 11:51 ` Markus Pargmann
2015-01-29 23:42 ` [Nbd] " Wouter Verhelst
2015-01-30 8:04 ` Markus Pargmann
2015-01-30 17:30 ` Wouter Verhelst [this message]
2015-01-31 12:38 ` Markus Pargmann
[not found] ` <CAECXXi5+VhBeZwZ5aosc+Oc+0bCZbJZTjzYA-QTRrJCjs2NFOw@mail.gmail.com>
2015-01-31 14:43 ` Andreas Klauer
2015-01-31 15:45 ` Markus Pargmann
2015-01-31 15:00 ` Markus Pargmann
2015-01-30 18:10 ` [Nbd] " H. Peter Anvin
2015-01-31 12:08 ` Markus Pargmann
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=20150130173014.GA16754@grep.be \
--to=w@uter.be \
--cc=Paul.Clements@steeleye.com \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mpa@pengutronix.de \
--cc=nbd-general@lists.sourceforge.net \
/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).