netdev - Re: [PATCH net-next 0/5] net: prefer listeners bound to an address

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: <20181214.155602.538530319219587326.davem@davemloft.net>
Date:   Fri, 14 Dec 2018 15:56:02 -0800 (PST)
From:   David Miller <davem@...emloft.net>
To:     posk@...gle.com
Cc:     netdev@...r.kernel.org, posk.devel@...il.com, edumazet@...gle.com
Subject: Re: [PATCH net-next 0/5] net: prefer listeners bound to an address

From: Peter Oskolkov <posk@...gle.com>
Date: Wed, 12 Dec 2018 13:15:32 -0800

> A relatively common use case is to have several IPs configured
> on a host, and have different listeners for each of them. We would
> like to add a "catch all" listener on addr_any, to match incoming
> connections not served by any of the listeners bound to a specific
> address.
> 
> However, port-only lookups can match addr_any sockets when sockets
> listening on specific addresses are present if so_reuseport flag
> is set. This patchset eliminates lookups into port-only hashtable,
> as lookups by (addr,port) tuple are easily available.
> 
> In a future patchset I plan to explore whether it is possible
> to remove port-only hashtables completely: additional refactoring
> will be required, as some non-lookup code uses the hashtables.

This looks great, series applied.

Thanks.