netdev - Re: [PATCH net-next 0/5] neighbor: More gc

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.154503.42220468190444967.davem@davemloft.net>
Date:   Fri, 14 Dec 2018 15:45:03 -0800 (PST)
From:   David Miller <davem@...emloft.net>
To:     dsahern@...nel.org
Cc:     netdev@...r.kernel.org, roopa@...ulusnetworks.com,
        dsahern@...il.com
Subject: Re: [PATCH net-next 0/5] neighbor: More gc_list changes

From: David Ahern <dsahern@...nel.org>
Date: Tue, 11 Dec 2018 18:57:20 -0700

> From: David Ahern <dsahern@...il.com>
> 
> More gc_list changes and cleanups.
> 
> The first 2 patches are bug fixes from the first gc_list change.
> Specifically, fix the locking order to be consistent - table lock
> followed by neighbor lock, and then entries in the FAILED state
> should always be candidates for forced_gc without waiting for any
> time span (return to the eviction logic prior to the separate gc_list).
> 
> Patch 3 removes 2 now unnecessary arguments to neigh_del.
> 
> Patch 4 moves a helper from a header file to core code in preparation
> for Patch 5 which removes NTF_EXT_LEARNED entries from the gc_list.
> These entries are already exempt from forced_gc; patch 5 removes them
> from consideration and makes them on par with PERMANENT entries given
> that they are also managed by userspace.

Series applied, thanks.