netdev - Re: [patch net-next 0/8] mlxsw: cleanup neigh handling

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: <20170206.112844.153468141426774611.davem@davemloft.net>
Date:   Mon, 06 Feb 2017 11:28:44 -0500 (EST)
From:   David Miller <davem@...emloft.net>
To:     jiri@...nulli.us
Cc:     netdev@...r.kernel.org, idosch@...lanox.com, eladr@...lanox.com,
        mlxsw@...lanox.com
Subject: Re: [patch net-next 0/8] mlxsw: cleanup neigh handling

From: Jiri Pirko <jiri@...nulli.us>
Date: Mon,  6 Feb 2017 16:20:09 +0100

> From: Jiri Pirko <jiri@...lanox.com>
> 
> Ido says:
> 
> This series addresses long standing issues in the mlxsw driver
> concerning neighbour reflection. It also prepares the code for follow-up
> changes dealing with proper resource cleanup and nexthop reflection.
> 
> The first two patches convert the neighbour reflection code to use an
> ordered workqueue, to prevent re-ordering of NEIGH_UPDATE events that
> may happen following subsequent patches.
> 
> The third to fifth patches remove the ndo_neigh_{construct,destroy}
> entry points from the driver, thereby relying only on NEIGH_UPDATE
> events for neighbour reflection. This simplifies the code considerably.
> 
> Last patches are fallout and adjust nits in the code I noticed while
> going over it.

Series applied, thanks.

Looks like 6lowpan is the only remaining user of the ndo_neigh_*() ops
now.