netdev - Re: [PATCH net-next 0/6] net: API and initial implementation for nexthop objects

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: <20190528.213837.678862722500953103.davem@davemloft.net>
Date:   Tue, 28 May 2019 21:38:37 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     dsahern@...nel.org
Cc:     netdev@...r.kernel.org, sharpd@...ulusnetworks.com,
        sworley@...ulusnetworks.com, dsahern@...il.com
Subject: Re: [PATCH net-next 0/6] net: API and initial implementation for
 nexthop objects

From: David Ahern <dsahern@...nel.org>
Date: Fri, 24 May 2019 14:43:02 -0700

> From: David Ahern <dsahern@...il.com>
> 
> This set contains the API and initial implementation for nexthops as
> standalone objects.
> 
> Patch 1 contains the UAPI and updates to selinux struct.
> 
> Patch 2 contains the barebones code for nexthop commands, rbtree
> maintenance and notifications.
> 
> Patch 3 then adds support for IPv4 gateways along with handling of
> netdev events.
> 
> Patch 4 adds support for IPv6 gateways.
> 
> Patch 5 has the implementation of the encap attributes. 
> 
> Patch 6 adds support for nexthop groups.
> 
> At the end of this set, nexthop objects can be created and deleted and
> userspace can monitor nexthop events, but ipv4 and ipv6 routes can not
> use them yet. Once the nexthop struct is defined, follow on sets add it
> to fib{6}_info and handle it within the respective code before routes
> can be inserted using them.

Series applied, I'll push this out after compile testing.

Thanks David.