From: David Ahern <dsahern@kernel.org>
To: Chen Linxuan <me@black-desk.cn>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
netdev@vger.kernel.org,
"Eric W. Biederman" <ebiederm@xmission.com>,
Lennart Poettering <lennart@poettering.net>,
Luca Boccassi <bluca@debian.org>
Subject: Re: [PATCH iproute2] ip/netns: avoid redundant mounts
Date: Sat, 28 Feb 2026 09:34:55 -0700 [thread overview]
Message-ID: <e6d22c18-d8f3-4b00-a4c2-d3a2890fcbca@kernel.org> (raw)
In-Reply-To: <CAC1kPDO=nQ4gGQKoHd-YT8sC3kitw=XHJcmEi61vjoJ3=b=+AQ@mail.gmail.com>
On 2/27/26 6:36 PM, Chen Linxuan wrote:
> On Sat, Feb 28, 2026 at 4:30 AM David Ahern <dsahern@kernel.org> wrote:
>>
>> On 2/24/26 6:21 PM, Chen Linxuan wrote:
>>>> with this patch I am still seeing 2 entries:
>>>>
>>>> $ sudo ./ip netns add blah
>>>> $ cat /proc/self/mountinfo | grep blah
>>>> 337 92 0:4 net:[4026532418] /run/netns/blah rw shared:344 - nsfs nsfs rw
>>>> 338 28 0:4 net:[4026532418] /run/netns/blah rw shared:344 - nsfs nsfs rw
>>>
>>> It seems like your old `ip` might have create the /run/netns mount point.
>>> After remove all netns then umount /run/netns, and ip netns add blah again.
>>> You should see only one entries.
>>
>> Fair point. I no longer have the patch, so send it again and I will try
>> a test in a new VM.
>
> Why has this patch been applied?
> https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=82c8b9fe511e6c503ef60c16eebc7a715c3189eb
>
> What is going on here?
>
ugh. my mistake after testing and noting the above; I did not drop the
commit. I'll re-test when I get some time.
prev parent reply other threads:[~2026-02-28 16:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 4:11 [PATCH iproute2] ip/netns: avoid redundant mounts Chen Linxuan via B4 Relay
2026-02-18 3:24 ` David Ahern
2026-02-25 1:21 ` Chen Linxuan
2026-02-27 20:30 ` David Ahern
2026-02-28 1:36 ` Chen Linxuan
2026-02-28 16:34 ` David Ahern [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=e6d22c18-d8f3-4b00-a4c2-d3a2890fcbca@kernel.org \
--to=dsahern@kernel.org \
--cc=bluca@debian.org \
--cc=ebiederm@xmission.com \
--cc=lennart@poettering.net \
--cc=me@black-desk.cn \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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