Received: by 2002:a25:868d:0:0:0:0:0 with SMTP id z13csp2770074ybk; Mon, 18 May 2020 07:32:36 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwSgR8rIHrIgiEeiKdm1gcnvXrdP2npuZjaeOSAZrxBRKVSJuIczCB5UOeJu9yjHiLCZzYn X-Received: by 2002:aa7:c5cb:: with SMTP id h11mr14432424eds.136.1589812356609; Mon, 18 May 2020 07:32:36 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1589812356; cv=none; d=google.com; s=arc-20160816; b=Ipsp1dLLbeBX78PN34nEc2TEV5iiKzETLeJFqGRcohR1Kz/pLwO8sMnCDdgDEBPCz4 teBR6jCnsTpyKf0ubuKUoubVKFBdDZTU1zYpWpQ6wBXwU9BxCRZgfUo+sdfFWm2mjoLe 2fihVPSQworDpZ+FiD3gLeDLYctl8iGZyHh8Uo8Nq4NyUFSBGf8XfbxpdkO9IVAmd+j8 f80iJc3dWyorRvlWKTE9D+Uj5K33gez58GUV5JZPzS59IKXQoDlnALY24kkfKd694ELf IXTxAWskWNBbHwJvtxrnqfhCGp0iW73Di935ufyokhKpW20X963X1At/7poihqsh+Dhc GBKw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:date:content-id:mime-version :subject:cc:to:references:in-reply-to:from:organization :dkim-signature; bh=/qLGWwr7pu6uwkkCaEo2q9GcnoY6Eg3hYnb4VN3qBPU=; b=xnc/DTuEEHIyy0K36saIw+fJqn1diGupJp+I2pQEl5mA7n/Lju01HxdBj3p1cBTly4 8cYCzq9mvgli+F7pGo0wkhkC5//Jk+z0oL9fVMsvWI5Y/1lS6Zg2cEa88tcWLG3shEYD ttT4eOUHDyDe7R6PT+s+GCwTWxSnKW+p0wR4D+wfCay6QDxAD3yYxjTMDhPzBgVDeUxH 6qZEIn6tVk+fYrvc5L9qv0N0f5qgQkpWZSzFu5JXcxuvDS/gTIBvdWOQ0wE/KX0HKThM bj4hYPqKaiU9HoR2gqS+Fw5b2HaEQDWUzNAvx+3VioYZMtjZ0fQGXJa1YfaLPSswFzwT uRRw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=EAX+Ye5r; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id d31si6985923edc.462.2020.05.18.07.32.11; Mon, 18 May 2020 07:32:36 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=EAX+Ye5r; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727823AbgEROal (ORCPT + 99 others); Mon, 18 May 2020 10:30:41 -0400 Received: from us-smtp-1.mimecast.com ([207.211.31.81]:47188 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727007AbgEROak (ORCPT ); Mon, 18 May 2020 10:30:40 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1589812239; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=/qLGWwr7pu6uwkkCaEo2q9GcnoY6Eg3hYnb4VN3qBPU=; b=EAX+Ye5r4M/iQO4Igog1cqP0euM1OqUQcVHXnQ7PFtkqcLy+42QwxxdbLCut5vs8Pm+bPG bOJ+nzlgK9ea9WKCQWFnYHpI8bD/wZ3H6XbLfTgiYuvPsTNVwoPbz4zWhH3405xw7T7KxU 0iwVAfN5N3j/H4rvfYP31AV6lXncNgs= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-201-fSgEJzz0PV2LPqGaVrE7Gw-1; Mon, 18 May 2020 10:30:38 -0400 X-MC-Unique: fSgEJzz0PV2LPqGaVrE7Gw-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 2166B80B71F; Mon, 18 May 2020 14:30:37 +0000 (UTC) Received: from warthog.procyon.org.uk (ovpn-112-95.rdu2.redhat.com [10.10.112.95]) by smtp.corp.redhat.com (Postfix) with ESMTP id 57E311001925; Mon, 18 May 2020 14:30:35 +0000 (UTC) Organization: Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903 From: David Howells In-Reply-To: References: To: mtk.manpages@gmail.com Cc: dhowells@redhat.com, Miklos Szeredi , Christian Brauner , lkml , "linux-fsdevel@vger.kernel.org" , Petr Vorel , linux-man Subject: Re: Setting mount propagation type in new mount API MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <909695.1589812234.1@warthog.procyon.org.uk> Date: Mon, 18 May 2020 15:30:34 +0100 Message-ID: <909768.1589812234@warthog.procyon.org.uk> X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Michael Kerrisk (man-pages) wrote: > I've been looking at the new mount API (fsopen(), fsconfig(), > fsmount(), move_mount(), etc.) and among the details that remain > mysterious to me is this: how does one set the propagation type > (private/shared/slave/unbindable) of a new mount and change the > propagation type of an existing mount? Christian said he was going to have a go at writing mount_setattr(). It's not trivial as it has to be able to handle AT_RECURSIVE. David