From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755263Ab2APUGf (ORCPT ); Mon, 16 Jan 2012 15:06:35 -0500 Received: from zeniv.linux.org.uk ([195.92.253.2]:52137 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754244Ab2APUGd (ORCPT ); Mon, 16 Jan 2012 15:06:33 -0500 Date: Mon, 16 Jan 2012 20:06:18 +0000 From: Al Viro To: Andy Lutomirski Cc: Casey Schaufler , Linus Torvalds , Jamie Lokier , Will Drewry , linux-kernel@vger.kernel.org, keescook@chromium.org, john.johansen@canonical.com, serge.hallyn@canonical.com, coreyb@linux.vnet.ibm.com, pmoore@redhat.com, eparis@redhat.com, djm@mindrot.org, segoon@openwall.com, rostedt@goodmis.org, jmorris@namei.org, scarybeasts@gmail.com, avi@redhat.com, penberg@cs.helsinki.fi, mingo@elte.hu, akpm@linux-foundation.org, khilman@ti.com, borislav.petkov@amd.com, amwang@redhat.com, oleg@redhat.com, ak@linux.intel.com, eric.dumazet@gmail.com, gregkh@suse.de, dhowells@redhat.com, daniel.lezcano@free.fr, linux-fsdevel@vger.kernel.org, linux-security-module@vger.kernel.org, olofj@chromium.org, mhalcrow@google.com, dlaor@redhat.com, corbet@lwn.net, alan@lxorguk.ukuu.org.uk Subject: Re: [PATCH 4/4] Allow unprivileged chroot when safe Message-ID: <20120116200618.GN23916@ZenIV.linux.org.uk> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Jan 15, 2012 at 04:37:21PM -0800, Andy Lutomirski wrote: > + is_chrooted = (fs->root.mnt->mnt_mountpoint != > + fs->root.mnt->mnt_parent->mnt_root || > + fs->root.dentry != fs->root.mnt->mnt_root); Folks, is it _that_ hard to at least try to compile your patches? Hint: this one will *not*. That sad detail aside, this test would have been a pile of garbage even on the kernels that used to have mnt_mountpoint in struct vfsmount. What *are* you trying to test here? The last part at least does make some sense - it's "process root happens to be the root of some vfsmount". The first part, though, makes no sense whatsoever; it's "... and that vfsmount is mounted on top of root of some other vfsmount". Grr... NAKed, with extreme prejudice.