netdev - Re: VRF Routing Rule Matching Issue: oif Rules Not Working After Commit 40867d74c374

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: <20250412131743.14507-1-hanhuihui5@huawei.com>
Date: Sat, 12 Apr 2025 21:17:43 +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: VRF Routing Rule Matching Issue: oif Rules Not Working After Commit 40867d74c374

On Tue, 8 Apr 2025 22:54:33 +0300 Ido Schimmel wrote:
>Before 40867d74c374 you couldn't match with FIB rules on oif/iif being a
>VRF slave because these fields in the flow structure were reset to the
>index of the VRF device in l3mdev_update_flow().
>
>I will try to check if we can interpret FIB rules with "oif" / "iif"
>pointing to a VRF as matching on "fl->flowi_l3mdev" rather than
>"fl->flowi_oif" / "fl->flowi_iif".
Thank you for your reply. Followed by a simple patch to restore the 
previous behavior, hopefully enlightening you.