From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.9 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id C4837C433E0 for ; Mon, 18 May 2020 14:30:41 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 8552220671 for ; Mon, 18 May 2020 14:30:41 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="EAX+Ye5r" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727777AbgEROal (ORCPT ); Mon, 18 May 2020 10:30:41 -0400 Received: from us-smtp-delivery-1.mimecast.com ([207.211.31.120]:43044 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727040AbgEROak (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-man-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-man@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