From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [patch 5/5] VFS: allow filesystem to override mknod capability checks Date: Fri, 21 Sep 2007 14:14:09 +0100 Message-ID: <20070921131409.GA9988@infradead.org> References: <20070921122343.307289079@szeredi.hu> <20070921123336.095183254@szeredi.hu> <20070921124504.GC8088@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: hch@infradead.org, akpm@linux-foundation.org, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org To: Miklos Szeredi Return-path: Received: from pentafluge.infradead.org ([213.146.154.40]:58844 "EHLO pentafluge.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751665AbXIUNOK (ORCPT ); Fri, 21 Sep 2007 09:14:10 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Fri, Sep 21, 2007 at 03:10:26PM +0200, Miklos Szeredi wrote: > Take this example: I've loopback mounted an UML disk image using fuse > (no privileges required), and want to create some device nodes. I > can't yet boot the UML because the device node is missing from the > image. So what should I do. Currently I have to manipulate the > mounted image as root. But that's really shouldn't be needed. That's something that shouldn't be solved in the filesystem, but rather through exact semantics of unprivilegued mounts. Given that an unprivilegued implies ignoring the device files we can easily allow users to create them, because they're nothing special anymore.