netdev - Re: [PATCH net 0/3] ipvlan: Deduplicate ipv4/ipv6 addr_validator

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] [day] [month] [year] [list]

Message-ID: <fd1c5142-b1cd-44a0-8b7b-3a21ab43a593@huawei.com>
Date: Fri, 23 Jan 2026 20:06:06 +0300
From: Dmitry Skorodumov <skorodumov.dmitry@...wei.com>
To: Jakub Kicinski <kuba@...nel.org>, Dmitry Skorodumov <dskr99@...il.com>
CC: <netdev@...r.kernel.org>
Subject: Re: [PATCH net 0/3] ipvlan: Deduplicate ipv4/ipv6
 addr_validator_event code

yes, sorry. It was a mechanical mistake from my side

Dmitry

On 20.01.2026 21:59, Jakub Kicinski wrote:
> On Tue, 20 Jan 2026 19:18:33 +0300 Dmitry Skorodumov wrote:
>> This is a bit stylish patches: The code to handle ipv4 and ipv6
>> address change are exactly the same. We don't need separate
>> functions for them. Just look whether we are called
>> with ipvlan_addr4_notifier_block or with ipvlan_addr6_notifier_block
> [PATCH net] is for fixes, please use [PATCH net-next] for cleanups.
> If these patches depend on your locking fix you'll need to wait
> with reposting until the fix appears in net-next (Thu afternoon).