netdev - Re: [PATCH RFC 1/3] ipv4: make flow functions more grepable by removing flowi4_init

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: <20160616.165930.1926303970829996171.davem@davemloft.net>
Date:	Thu, 16 Jun 2016 16:59:30 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	hannes@...essinduktion.org
Cc:	dsa@...ulusnetworks.com, netdev@...r.kernel.org, ja@....bg
Subject: Re: [PATCH RFC 1/3] ipv4: make flow functions more grepable by
 removing flowi4_init_output

From: Hannes Frederic Sowa <hannes@...essinduktion.org>
Date: Thu, 16 Jun 2016 23:39:12 +0200

> Most of the time a new attribute that gets added to flow4i only
> decreases the scope of the actual lookup, thus a missing attribute
> doesn't necessarily indicate a bug.

That's true, and it works well so long as the value zero provides
the behavior that existed before the new flow key was added.