Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751521Ab3GXMtf (ORCPT ); Wed, 24 Jul 2013 08:49:35 -0400 Received: from static.92.5.9.176.clients.your-server.de ([176.9.5.92]:47264 "EHLO hallynmail2" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750909Ab3GXMte (ORCPT ); Wed, 24 Jul 2013 08:49:34 -0400 Date: Wed, 24 Jul 2013 12:49:33 +0000 From: "Serge E. Hallyn" To: "Eric W. Biederman" Cc: Andy Lutomirski , Linux Containers , "Serge E. Hallyn" , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org Subject: Re: [REVIEW][PATCH] vfs: Lock in place mounts from more privileged users Message-ID: <20130724124933.GA16517@mail.hallyn.com> References: <877gghruwq.fsf@xmission.com> <87li4wpi2b.fsf@xmission.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87li4wpi2b.fsf@xmission.com> 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 Content-Length: 724 Lines: 17 Quoting Eric W. Biederman (ebiederm@xmission.com): > > Serge does this patch break lxc? I think all should be well but I want > to make certain there is not some hidden case where this fundamentaly > breaks some functionality. I haven't yet tried. I'll build and test a kernel today. I'm pretty sure all the child's mounts are done after clone, so I *think* the worst case will be that the unmounting of put_old after pivot_root() will be noisy. Will let you know. -serge -- 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/