netdev - Re: [PATCH v2 0/2] ipv4: Make neigh lookup keys for loopback/point-to-point devices be INADDR

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 15 Jan 2018 14:54:07 -0500 (EST)
From:   David Miller <davem@...emloft.net>
To:     jwestfall@...realistic.net
Cc:     netdev@...r.kernel.org
Subject: Re: [PATCH v2 0/2] ipv4: Make neigh lookup keys for
 loopback/point-to-point devices be INADDR_ANY 

From: Jim Westfall <jwestfall@...realistic.net>
Date: Sun, 14 Jan 2018 04:18:49 -0800

> This used to be the previous behavior in older kernels but became broken in
> a263b3093641f (ipv4: Make neigh lookups directly in output packet path)
> and then later removed because it was broken in 0bb4087cbec0 (ipv4: Fix neigh
> lookup keying over loopback/point-to-point devices)
> 
> Not having this results in there being an arp entry for every remote ip
> address that the device talks to.  Given a fairly active device it can
> cause the arp table to become huge and/or having to add/purge large number
> of entires to keep within table size thresholds.
...
> v2: 
>  - fixes coding style issues

Series applied and queued up for -stable, thank you.