public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@inria.fr>
To: viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, corbet@lwn.net,
	linux-doc@vger.kernel.org
Subject: question about sharedsubtree.rst
Date: Sun, 26 Jul 2020 18:06:11 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.22.394.2007261801150.13826@hadrien> (raw)

Hello,

Documentation/filesystems/sharedsubtree.rst contains the following:

        ->mnt_flags
	        takes two more flags to indicate the propagation status of
	        the vfsmount.  MNT_SHARE indicates that the vfsmount is a shared
	        vfsmount.  MNT_UNCLONABLE indicates that the vfsmount cannot be
		replicated.

I guess that MNT_SHARE should be MNT_SHARED.  More seriously,
MNT_UNCLONABLE seems to have never existed, except in a patch proposed in
2005: https://lists.linuxcoding.com/kernel/2005-q3/msg01881.html
Should there be a description of MNT_UNBINDABLE instead?  Or something
else?

thanks,
julia

                 reply	other threads:[~2020-07-26 16:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.22.394.2007261801150.13826@hadrien \
    --to=julia.lawall@inria.fr \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox