From: no-reply@sashiko.virtuozzo.com
To: khorenko@virtuozzo.com, "Denis V. Lunev" <den@openvz.org>
Cc: Andrii Mozharovskyi <andrii.mozharovskyi@virtuozzo.com>,
devel@openvz.org
Subject: Re: [Devel] [PATCH hci-8.1] ve/proc/net: fix tcp6 and udp6 missing from /proc/net in containers
Date: Fri, 6 Nov 2026 12:23:49 +0000 [thread overview]
Message-ID: <010701a1b0d0b161-65d82bae-0efa-48f6-a32b-3d601d6f7803-000000@eu-central-1.amazonses.com> (raw)
In-Reply-To: <20261106121957.3696406-1-den@openvz.org>
> From: Denis V. Lunev <den@openvz.org>
>
> A container sees /proc/net/tcp and udp but gets ENOENT on tcp6 and udp6,
> both at /proc/net and at /proc/<pid>/net. Applications that parse these
> tables, like the .NET startup script in JE-76965, fail although IPv6
> works and ss lists the sockets over netlink.
>
> In vz7 all of tcp, tcp6, udp, udp6, udplite and udplite6 were created by
> tcp_proc_register() and udp_proc_register(), which used the VE helper,
> so one call covered every family. Upstream commit 37d849bb4294
> ("ipv{4,6}/tcp: simplify procfs registration") and commit a3d2599b2446
> ("ipv{4,6}/udp{,lite}: simplify proc registration") moved each family to
> its own proc_create_net_data() call, and the port of the VE patch
> converted only the IPv4 tcp and udp ones. udplite and udplite6 are
> hidden the same way. icmp6 did not exist in vz7 and was never converted,
> while its IPv4 twin icmp is visible.
>
> Register the five entries with the VE helpers. They are per-netns and
> their seq iterators skip sockets of other namespaces, so a container
> lists only its own sockets.
>
> https://virtuozzo.atlassian.net/browse/VSTOR-153793
>
> Fixes: 68eae6367fdc ("ve/proc/net: virtualize all the network proc entries")
> Reported-by: Andrii Mozharovskyi <andrii.mozharovskyi@virtuozzo.com>
> Feature: procfs: virtualize /proc/net/* entries
> Signed-off-by: Denis V. Lunev <den@openvz.org>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.vzint.dev/#/patchset/20261106121957.3696406-1-den@openvz.org?part=1
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
prev parent reply other threads:[~2026-11-06 12:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 12:19 Denis V. Lunev
2026-11-06 12:23 ` no-reply [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=010701a1b0d0b161-65d82bae-0efa-48f6-a32b-3d601d6f7803-000000@eu-central-1.amazonses.com \
--to=no-reply@sashiko.virtuozzo.com \
--cc=andrii.mozharovskyi@virtuozzo.com \
--cc=den@openvz.org \
--cc=devel@openvz.org \
--cc=khorenko@virtuozzo.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