netdev - Re: [PATCH net-next 00/14] ipmr, ip6mr: Allow MC-routing locally-generated MC packets

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87wm9jeo3n.fsf@nvidia.com>
Date: Tue, 10 Jun 2025 15:12:55 +0200
From: Petr Machata <petrm@...dia.com>
To: Jakub Kicinski <kuba@...nel.org>
CC: Petr Machata <petrm@...dia.com>, "David S. Miller" <davem@...emloft.net>,
	Eric Dumazet <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>, "David
 Ahern" <dsahern@...il.com>, <netdev@...r.kernel.org>, Simon Horman
	<horms@...nel.org>, Nikolay Aleksandrov <razor@...ckwall.org>, Ido Schimmel
	<idosch@...dia.com>, <mlxsw@...dia.com>
Subject: Re: [PATCH net-next 00/14] ipmr, ip6mr: Allow MC-routing
 locally-generated MC packets


Jakub Kicinski <kuba@...nel.org> writes:

> On Mon, 9 Jun 2025 22:50:16 +0200 Petr Machata wrote:
>> Multicast routing is today handled in the input path. Locally generated MC
>> packets don't hit the IPMR code. Thus if a VXLAN remote address is
>> multicast, the driver needs to set an OIF during route lookup. In practice
>> that means that MC routing configuration needs to be kept in sync with the
>> VXLAN FDB and MDB. Ideally, the VXLAN packets would be routed by the MC
>> routing code instead.
>
> I think this leads to kmemleaks:
> [...]
> hit by netdevsim udp_tunnel_nic.sh

Thanks, I'll take a look.

> Also, do you have a branch with the iproute2 patches we could pull 
> in the CI?

My bad, didn't think of it:
https://github.com/pmachata/iproute2/commits/vxlan_mc_ul/