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: <1e104885-f882-b4c1-7fef-604f6f6fe9d8@gmail.com>
Date:   Thu, 25 Jan 2018 10:34:09 -0700
From:   David Ahern <dsahern@...il.com>
To:     Serhey Popovych <serhe.popovych@...il.com>, netdev@...r.kernel.org
Subject: Re: [PATCH iproute2-next v3 0/8] ip: Introduce and use
 get_addr_rta()/inet_addr_match_rta()

On 1/24/18 11:56 AM, Serhey Popovych wrote:
> Now we enhance get_addr() to return additional information about address
> (e.g. if it unspecified or multicast) we want to have same functionality
> for attributes in netlink message.
> 
> Introduce and use get_addr_rta() that parses given netlink attribute
> into @inet_prefix data structure in the same way similar get_addr()
> parses address from it's string representation.
> 
> Use attribute length to guess address family: force it by giving non
> AF_UNSPEC @family to get_addr_rta() to ensure address is of expected
> family.
> 
> Introduce and use inet_addr_match_rta() to further simplify and unify
> code where get_addr_rta() intended to be used together with
> inet_addr_match().
> 
> This is next step in ipv4 and ipv6 modules unification to prepare for
> merge in the future.
> 


series applied to iproute2-next. Thanks, Serhey.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ