From: Martin Mares Subject: Re: [PATCH] private mounts Date: Wed, 27 Apr 2005 20:25:28 +0200 Message-ID: <20050427182528.GD4241@ucw.cz> References: <20050427092450.GB1819@elf.ucw.cz> <20050427143126.GB1957@mail.shareable.org> <20050427153320.GA19065@atrey.karlin.mff.cuni.cz> <20050427155022.GR4431@marowsky-bree.de> <20050427164652.GA3129@ucw.cz> <20050427175425.GA4241@ucw.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: lmb@suse.de, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org Return-path: Received: from albireo.ucw.cz ([84.242.65.67]:28290 "EHLO albireo.ucw.cz") by vger.kernel.org with ESMTP id S261933AbVD0SZa (ORCPT ); Wed, 27 Apr 2005 14:25:30 -0400 To: Miklos Szeredi Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Hello! > So yes the check fsuid is not the perfect solution. However let me > remind you that neither is the one with private namespace. What I'm arguing about is that the fsuid check is obscure (it breaks traditional semantics of file permissions [*], it doesn't allow an user to grant access to his user mount to other users, even if the permissions allow that and so on) and it doesn't fully solve the problem anyway. For similar reasons, I don't advocate for private namespaces either. The cure more likely lies in simple policy rules like the "all user mounts belong to /mnt/usr" one, instead of putting dubious policy to the kernel. Have a nice fortnight -- Martin `MJ' Mares http://atrey.karlin.mff.cuni.cz/~mj/ Faculty of Math and Physics, Charles University, Prague, Czech Rep., Earth Mr. Worf, scan that ship." "Aye, Captain... 600 DPI?