Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934227AbbKSOh5 (ORCPT ); Thu, 19 Nov 2015 09:37:57 -0500 Received: from out5-smtp.messagingengine.com ([66.111.4.29]:55890 "EHLO out5-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934059AbbKSOhy (ORCPT ); Thu, 19 Nov 2015 09:37:54 -0500 Message-Id: <1447943873.2240617.444348369.7F817E6C@webmail.messagingengine.com> X-Sasl-Enc: +kwCP72a8a+LVUTgpGRd5bPIFrALUNxIBGzdp8jPXcgX 1447943873 From: Colin Walters To: Richard Weinberger , James Morris Cc: Al Viro , Seth Forshee , Austin S Hemmelgarn , "Eric W. Biederman" , linux-bcache@vger.kernel.org, "device-mapper development" , linux-raid@vger.kernel.org, linux-mtd@lists.infradead.org, "linux-fsdevel" , LSM , selinux@tycho.nsa.gov, Serge Hallyn , Andy Lutomirski , LKML , "Theodore Ts'o" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - ajax-dab2dbe4 In-Reply-To: <564D7FF6.50408@nod.at> References: <20151117172551.GA108807@ubuntu-hedt> <20151117175506.GW22011@ZenIV.linux.org.uk> <564B79B1.3040207@gmail.com> <20151117191606.GC108807@ubuntu-hedt> <564B941A.2070601@gmail.com> <20151117213255.GE108807@ubuntu-hedt> <564C6DD4.6090308@gmail.com> <20151118142238.GB134139@ubuntu-hedt> <20151118145818.GC22011@ZenIV.linux.org.uk> <20151118150512.GE134139@ubuntu-hedt> <20151118151335.GD22011@ZenIV.linux.org.uk> <564D7FF6.50408@nod.at> Subject: Re: [PATCH v3 0/7] User namespace mount updates Date: Thu, 19 Nov 2015 09:37:53 -0500 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 958 Lines: 22 On Thu, Nov 19, 2015, at 02:53 AM, Richard Weinberger wrote: > Erm, I don't want this in the kernel. That's why I've proposed the lklfuse approach. I already said this before but just to repeat, since I'm confused: How would "lklfuse" be different from http://libguestfs.org/ which we at Red Hat (and a number of other organizations) use quite widely now for build systems, debugging etc. In the end it's just running the kernel in KVM with a custom protocol, with support for non-filesystem things like "install a bootloader", and it already supports FUSE. I'm pretty firmly with Al here - the attack surface increase here is too great, and we'd likely turn this off if it even did make it into the kernel. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/