linux-kernel - [RFC 0/4] nbd: root device support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 13 Jan 2015 14:44:21 +0100
From:	Markus Pargmann <mpa@...gutronix.de>
To:	Paul Clements <Paul.Clements@...eleye.com>
Cc:	nbd-general@...ts.sourceforge.net, linux-kernel@...r.kernel.org,
	kernel@...gutronix.de, Markus Pargmann <mpa@...gutronix.de>
Subject: [RFC 0/4] nbd: root device support

Hi,

This series adds root device support to nbd. The last patch contains a simple
and small implementation of the nbd-client to make the nbd negotiation. After
the negotiation, the socket is bound to nbd0 so the rootfs can be mounted from
nbd0. The connection parameters are passed as module parameter in the following
format:
	nbd.root_server=[<SERVER_IP>:]<SERVER_PORT>/<EXPORT_NAME>

Patches 2 and 3 are preparation patches for patch 4 which adds nbd-root.

Patch 4 uses blkdev_get_by_dev() at the moment to get the blockdevice for a
specific nbd_device. However the documentation of blkdev_get_by_dev() states
that the function should not be used. I couldn't find any better way to get
the blockdevice so I would appreciate any suggestions on how to do it correctly.

Best regards,

Markus


Markus Pargmann (4):
  nbd: Replace kthread_create with kthread_run
  nbd: Split 'DO_IT' into three functions
  nbd: Create helper functions for ioctls
  nbd: Add support for nbd as root device

 drivers/block/nbd.c | 531 ++++++++++++++++++++++++++++++++++++++++++++--------
 1 file changed, 454 insertions(+), 77 deletions(-)

-- 
2.1.4

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/