linux-kernel - Re: [RFC PATCH 1/2] loop: Add loop filesystem

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <53851835.3060706@infradead.org>
Date:	Tue, 27 May 2014 15:56:53 -0700
From:	Randy Dunlap <rdunlap@...radead.org>
To:	Seth Forshee <seth.forshee@...onical.com>,
	linux-kernel@...r.kernel.org, lxc-devel@...ts.linuxcontainers.org
CC:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Alexander Viro <viro@...iv.linux.org.uk>,
	James Bottomley <James.Bottomley@...senPartnership.com>,
	Serge Hallyn <serge.hallyn@...ntu.com>,
	"Michael H. Warfield" <mhw@...tsend.com>,
	Marian Marinov <mm@...com>,
	Eric Biederman <ebiederm@...ssion.com>,
	Richard Weinberger <richard.weinberger@...il.com>,
	Andy Lutomirski <luto@...capital.net>,
	Michael J Coss <michael.coss@...atel-lucent.com>
Subject: Re: [RFC PATCH 1/2] loop: Add loop filesystem

On 05/27/2014 02:58 PM, Seth Forshee wrote:
> Add limited capability for use of loop devices in containers via
> a loopfs psuedo fs. When mounted this filesystem will contain
> only a loop-control device node. This can be used to request free
> loop devices which will be "owned" by that mount. Device nodes
> appear automatically for these devices, and the same device will
> not be given to another loopfs mount. Privileged loop ioctls
> (for encrypted loop) will be allowed within the namespace which
> mounted the loopfs.
> 
> Privileged block ioctls are not permitted, so features such as
> partitions are not supported for unprivileged users.
> 
> Signed-off-by: Seth Forshee <seth.forshee@...onical.com>
> ---
>  drivers/block/loop.c       | 110 +++++++++++---
>  drivers/block/loop.h       |   2 +
>  fs/Makefile                |   1 +
>  fs/loopfs/Makefile         |   6 +
>  fs/loopfs/inode.c          | 349 +++++++++++++++++++++++++++++++++++++++++++++
>  include/linux/loopfs.h     |  46 ++++++
>  include/uapi/linux/magic.h |   1 +
>  7 files changed, 495 insertions(+), 20 deletions(-)
>  create mode 100644 fs/loopfs/Makefile
>  create mode 100644 fs/loopfs/inode.c
>  create mode 100644 include/linux/loopfs.h
> 

> diff --git a/fs/loopfs/Makefile b/fs/loopfs/Makefile
> new file mode 100644
> index 000000000000..01aedfb2f841
> --- /dev/null
> +++ b/fs/loopfs/Makefile
> @@ -0,0 +1,6 @@
> +#
> +# Makefile for the loopfs virtual filesystem
> +#
> +
> +obj-$(CONFIG_BLK_DEV_LOOP)		+= loopfs.o
> +loopfs-$(CONFIG_BLK_DEV_LOOP)		:= inode.o

I guess that you need to update the BLK_DEV_LOOP entry in
drivers/block/Kconfig to mention this?


-- 
~Randy
--
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/