linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: luca.boccassi@gmail.com
To: alx@kernel.org
Cc: cyphar@cyphar.com, linux-man@vger.kernel.org
Subject: [PATCH v2] man/man2/move_mount.2: document EINVAL on multiple instances
Date: Mon,  6 Oct 2025 12:29:58 +0100	[thread overview]
Message-ID: <20251006113122.511990-1-luca.boccassi@gmail.com> (raw)
In-Reply-To: <20251006103852.506614-1-luca.boccassi@gmail.com>

From: Luca Boccassi <luca.boccassi@gmail.com>

open_tree() with OPEN_TREE_CLONE is needed to apply a mount multiple
times, otherwise EINVAL is returned by move_mount(). Available since 6.15.

Signed-off-by: Luca Boccassi <luca.boccassi@gmail.com>
---
As requested by Aleksa on https://github.com/brauner/man-pages-md/pull/19
and based on the 'fs' branch where move_mount(2) was added

v2: semantic line break, clarify purpose of mentioning a version

 man/man2/move_mount.2 | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/man/man2/move_mount.2 b/man/man2/move_mount.2
index 13063ac1f..968e6a81a 100644
--- a/man/man2/move_mount.2
+++ b/man/man2/move_mount.2
@@ -457,6 +457,14 @@ which would otherwise cause the unbindable mounts to be propagated
 was attempted,
 but one of the listed restrictions was violated.
 .TP
+.B EINVAL
+The source mount is already mounted somewhere else.
+Since Linux 6.15 it is possible to clone the mount via
+.BR open_tree (2)
+with
+.B \%OPEN_TREE_CLONE
+and use that as the source to avoid this error.
+.TP
 .B ELOOP
 Too many symbolic links encountered
 when resolving one of
-- 
2.47.3


      parent reply	other threads:[~2025-10-06 11:31 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-06 10:38 [PATCH] man/man2/move_mount.2: document EINVAL on multiple instances luca.boccassi
2025-10-06 11:19 ` Alejandro Colomar
2025-10-06 11:32   ` Luca Boccassi
2025-10-06 11:42     ` Alejandro Colomar
2025-10-06 11:46       ` Luca Boccassi
2025-10-06 11:57         ` Alejandro Colomar
2025-10-06 12:28           ` Luca Boccassi
2025-10-06 12:37             ` Alejandro Colomar
2025-10-06 13:11               ` Alejandro Colomar
2025-10-06 13:40             ` Aleksa Sarai
2025-10-06 13:44               ` Luca Boccassi
2025-10-07 18:37                 ` Aleksa Sarai
2025-10-07 18:38                   ` Luca Boccassi
2025-10-12  6:14                 ` Askar Safin
2025-10-12  9:40                   ` Luca Boccassi
2025-10-12 11:27                     ` Askar Safin
2025-10-12 12:58                     ` Askar Safin
2025-10-12 13:16                       ` Alejandro Colomar
2025-10-13  5:51                         ` Askar Safin
2025-10-12 14:25                       ` Luca Boccassi
2025-10-12 14:57                         ` Alejandro Colomar
2025-10-12 18:57                           ` G. Branden Robinson
2025-10-16 10:29                             ` Alejandro Colomar
2025-10-13  4:14                         ` Askar Safin
2025-10-22  7:36                 ` Christian Brauner
2025-10-06 11:29 ` luca.boccassi [this message]

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=20251006113122.511990-1-luca.boccassi@gmail.com \
    --to=luca.boccassi@gmail.com \
    --cc=alx@kernel.org \
    --cc=cyphar@cyphar.com \
    --cc=linux-man@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).