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] [day] [month] [year] [list]
Message-Id: <20190417.231639.263308047959155510.davem@davemloft.net>
Date:   Wed, 17 Apr 2019 23:16:39 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     dsahern@...nel.org
Cc:     netdev@...r.kernel.org, idosch@...lanox.com, dsahern@...il.com
Subject: Re: [PATCH v2 net-next 00/13] ipv6: Use fib6_result for fib_lookups

From: David Ahern <dsahern@...nel.org>
Date: Tue, 16 Apr 2019 14:35:58 -0700

> From: David Ahern <dsahern@...il.com>
> 
> Add fib6_result as a single data structure to hold results from a fib
> lookup. IPv6 currently has everything in 1 data structure - a fib6_info,
> but with nexthop objects the fib6_nh can be in a nexthop or a nexthop
> can be a blackhole which affects the fib6_type and flags (REJECT).
> 
> v2
> - fixed 2 bugs in patch12:
>   i. checking return from fib6_table_lookup in fib6_lookup
>   ii. call to fib6_rule_saddr in fib6_rule_action_alt should use res->nh

Looks good, series applied.

Thanks David.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ