netdev - Re: [PATCH 0/2] Allow rules to track originating protocol

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: <20180219.112414.1368003412958614845.davem@davemloft.net>
Date:   Mon, 19 Feb 2018 11:24:14 -0500 (EST)
From:   David Miller <davem@...emloft.net>
To:     sharpd@...ulusnetworks.com
Cc:     netdev@...r.kernel.org
Subject: Re: [PATCH 0/2] Allow rules to track originating protocol

From: Donald Sharp <sharpd@...ulusnetworks.com>
Date: Sat, 17 Feb 2018 07:31:46 -0500

> Add the ability for the kernel to track the originating protocol
> for when new rules are added to the kernel.

I think you need to collapse these two patches together.

The first patch will create a situation where VRF rules cannot be
deleted properly since the protocol field is not being initialized,
and that would be a regression.

Thank you.