From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com ([209.132.183.28]:34748 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728149AbeIUV0y (ORCPT ); Fri, 21 Sep 2018 17:26:54 -0400 From: David Howells In-Reply-To: References: <20180920151214.15484-1-mszeredi@redhat.com> <20180920151214.15484-6-mszeredi@redhat.com> <17157.1537542475@warthog.procyon.org.uk> To: Miklos Szeredi Cc: dhowells@redhat.com, Miklos Szeredi , Al Viro , Christian Brauner , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 5/6] fsmount: do not use legacy MS_ flags MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <8491.1537544247.1@warthog.procyon.org.uk> Date: Fri, 21 Sep 2018 16:37:27 +0100 Message-ID: <8492.1537544247@warthog.procyon.org.uk> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Miklos Szeredi wrote: > Indeed. Also, shouldn't these include the propagation flags? I guess so, though I'd be tempted to put those in a separate set. Also, I'm not sure whether fsmount() should deal with prop flags or whether that should be something move_mount() needs to deal with (ie. does propagation need applying at the time of splicing, depending on the parent). David