From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com ([209.132.183.28]:56242 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726503AbeJJTSV (ORCPT ); Wed, 10 Oct 2018 15:18:21 -0400 From: David Howells In-Reply-To: References: <153754740781.17872.7869536526927736855.stgit@warthog.procyon.org.uk> <153754743491.17872.12115848333103740766.stgit@warthog.procyon.org.uk> To: Alan Jenkins Cc: dhowells@redhat.com, viro@zeniv.linux.org.uk, torvalds@linux-foundation.org, ebiederm@xmission.com, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, mszeredi@redhat.com Subject: Re: [PATCH 03/34] teach move_mount(2) to work with OPEN_TREE_CLONE [ver #12] MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <30812.1539172590.1@warthog.procyon.org.uk> Content-Transfer-Encoding: 8BIT Date: Wed, 10 Oct 2018 12:56:30 +0100 Message-ID: <30813.1539172590@warthog.procyon.org.uk> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Alan Jenkins wrote: > I replied last time to wonder about the MNT_UMOUNT mnt_flag. So I've tested it > now :-), on David's current tree (commit 5581f4935add). > > The modified do_move_mount() allows re-attaching something that was > lazy-unmounted. But the lazy unmount sets MNT_UMOUNT. And this flag is not > cleared when the mount is re-attached. Sorry, yes. I'm not sure what the best way to deal with this is. Should it just return -EPERM or -ESTALE if MNT_UMOUNT is set? David