OpenVZ / Virtuozzo kernel development (devel@openvz.org)
 help / color / mirror / Atom feed
From: Konstantin Khorenko <khorenko@virtuozzo.com>
To: "Denis V. Lunev" <den@openvz.org>
Cc: devel@openvz.org,
	Andrii Mozharovskyi <andrii.mozharovskyi@virtuozzo.com>
Subject: Re: [Devel] [PATCH hci-8.1] ve/proc/net: fix tcp6 and udp6 missing from /proc/net in containers
Date: Tue, 10 Nov 2026 17:12:48 +0100	[thread overview]
Message-ID: <179432716898.3523994.4480555659028785280.b4-review@b4> (raw)
In-Reply-To: <20261106121957.3696406-1-den@openvz.org>

Applying with these fixes on my side:
- "so one call covered every family" -> "so one helper served every
  family"
- the vz7 / upstream / udplite+icmp6 paragraph split in three

On 11/6/26 13:19, Denis V. Lunev wrote:
> 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

In vz7 every family made its own call, e.g. tcp6_proc_init_net() ->
tcp_proc_register(net, &tcp6_seq_afinfo); what they shared was the
helper.

> 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.

Three topics in one paragraph; split at each turn so it reads at a
glance.

-- 
Konstantin Khorenko,
Virtuozzo Linux Kernel Team

_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel

  parent reply	other threads:[~2026-11-10 16:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-06 12:19 Denis V. Lunev
2026-11-06 12:23 ` no-reply
2026-11-10 16:12 ` Konstantin Khorenko [this message]
2026-11-10 16:12 ` Konstantin Khorenko

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=179432716898.3523994.4480555659028785280.b4-review@b4 \
    --to=khorenko@virtuozzo.com \
    --cc=andrii.mozharovskyi@virtuozzo.com \
    --cc=den@openvz.org \
    --cc=devel@openvz.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