From: Askar Safin <safinaskar@gmail.com>
To: luca.boccassi@gmail.com
Cc: alx@kernel.org, brauner@kernel.org, cyphar@cyphar.com,
linux-fsdevel@vger.kernel.org, linux-man@vger.kernel.org
Subject: Re: [PATCH] man/man2/move_mount.2: document EINVAL on multiple instances
Date: Sun, 12 Oct 2025 09:14:38 +0300 [thread overview]
Message-ID: <20251012061438.283584-1-safinaskar@gmail.com> (raw)
In-Reply-To: <CAMw=ZnQki4YR24CfYJMAEWEAQ63yYer-YzSAeH+xFA-fNth-XQ@mail.gmail.com>
Luca Boccassi <luca.boccassi@gmail.com>:
> Almost - the use case is that I prep an image as a detached mount, and
> then I want to apply it multiple times, without having to reopen it
> again and again. If I just do 'move_mount()' multiple times, the
> second one returns EINVAL. From 6.15, I can do open_tree with
> OPEN_TREE_CLONE before applying with move_mount, and everything works.
This sounds like a bug. Please, give all reproduction steps. Both for
EINVAL and for non-working open_tree before 6.15. I want to reproduce it.
--
Askar Safin
next prev parent reply other threads:[~2025-10-12 6:14 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 [this message]
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 ` [PATCH v2] " luca.boccassi
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=20251012061438.283584-1-safinaskar@gmail.com \
--to=safinaskar@gmail.com \
--cc=alx@kernel.org \
--cc=brauner@kernel.org \
--cc=cyphar@cyphar.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=luca.boccassi@gmail.com \
/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).