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: Mon, 13 Oct 2025 07:14:59 +0300 [thread overview]
Message-ID: <20251013041459.148478-1-safinaskar@gmail.com> (raw)
In-Reply-To: <CAMw=ZnTuK=ZijDbhrMOXmiGjs=8i2qyQUwwtM9tcvTSP0k6H4g@mail.gmail.com>
Luca Boccassi <luca.boccassi@gmail.com>:
> I don't think so. This was in a mount namespace, so it was not shared,
If it was not shared, then this seems like a bug. Please, say me
reproduction steps, I will try to fix the bug.
If you don't have reproduction steps, then, at very least, say something
like "this happens at line xxx of this big program".
Also, note that "unshare(CLONE_NEWNS)" and "unshare --mount" behave
differently: if you do "unshare(CLONE_NEWNS)", then all shared mounts
continue to be shared. But if you do "unshare --mount", then it
internally does "unshare(CLONE_NEWNS)" and then equivalent of
"mount --make-rprivate", i. e. makes all mounts inside new namespace
private.
> it was a new image, so not shared either, and '/' was not involved at
When you make a new mount under existing shared mount, it becomes shared, too.
(I just checked this.) Also, on systemd, all mounts (not only '/') are shared
by default, I just checked this, too.
--
Askar Safin
prev parent reply other threads:[~2025-10-13 4:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251006103852.506614-1-luca.boccassi@gmail.com>
[not found] ` <2hg43wshc3iklydtwx25ulqadzyuldkyi6wylgztzwendi5zhw@kw223cxay7qn>
[not found] ` <CAMw=ZnR6QMNevxtxWysqi5UkDmbD68Ge=R5cVAxskqtmhb5m5A@mail.gmail.com>
[not found] ` <bywtfrezkfevzz7y2ecq4w75nfjhz2qqu2cugwl3ml57jlom5k@b5bebz4f24sd>
[not found] ` <CAMw=ZnSZmW=BFbLLSKsn7sze-FXZroQw6o4eJU9675VmGjzDRw@mail.gmail.com>
[not found] ` <rleqiwn4mquteybmica3jwilel3mbmaww5p3wr7ju7tfj2d6wt@g6rliisekp2e>
[not found] ` <CAMw=ZnTDw59GqW-kQkf1aTEHgmBRzcD0z9Rk+wpE_REEmaEJBw@mail.gmail.com>
2025-10-06 13:40 ` [PATCH] man/man2/move_mount.2: document EINVAL on multiple instances 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-13 4:14 ` Askar Safin [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=20251013041459.148478-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).