netdev - Re: [PATCH] resume oif rule match l3mdev in fib

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: <20250415141100.33811-1-hanhuihui5@huawei.com>
Date: Tue, 15 Apr 2025 22:11:00 +0800
From: hanhuihui <hanhuihui5@...wei.com>
To: <idosch@...sch.org>
CC: <dsahern@...nel.org>, <hanhuihui5@...wei.com>, <kuba@...nel.org>,
	<netdev@...r.kernel.org>
Subject: Re: [PATCH] resume oif rule match l3mdev in fib_lookup

On Mon, 14 Apr 2025 20:24:11 +0300, Ido Schimmel wrote:
>On Mon, Apr 14, 2025 at 10:17:35AM +0300, Ido Schimmel wrote:
..
>> This will prevent us from matching on the output device when the device
>> is enslaved to a VRF. We should try to match on L3 domain only if the
>> FIB rule matches on a VRF device. I will try to send a fix today (wasn't
>> feeling well in the last few days).
>
>Posted a fix:
>https://lore.kernel.org/netdev/20250414172022.242991-2-idosch@nvidia.com/
>
>Can you please test it and tag it if it fixes your issue?

Tested-by: hanhuihui hanhuihui5@...wei.com

The patch successfully resolves the VRF oif rule matching issue. The FIB lookup now correctly identifies 
the L3 domain when using VRFs. Thank you for the quick fix.