netdev - Re: [RFC] iproute: Add support for extended ack to rtnl

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: <60f33e91-2dfc-e70b-67bc-133484a47e3c@mojatatu.com>
Date:   Thu, 4 May 2017 11:50:10 -0400
From:   Jamal Hadi Salim <jhs@...atatu.com>
To:     David Miller <davem@...emloft.net>, dsahern@...il.com
Cc:     daniel@...earbox.net, stephen@...workplumber.org,
        netdev@...r.kernel.org
Subject: Re: [RFC] iproute: Add support for extended ack to rtnl_talk

On 17-05-04 10:41 AM, David Miller wrote:
> From: David Ahern <dsahern@...il.com>
> Date: Thu, 4 May 2017 08:27:35 -0600
>
>> On 5/4/17 3:36 AM, Daniel Borkmann wrote:
>>> What is the clear benefit/rationale of outsourcing this to
>>> libmnl? I always was the impression we should strive for as little
>>> dependencies as possible?
>>
>> +1
>
> Agreed, all else being equal iproute2 should be as self contained
> as possible since it is such a fundamental tool.
>

True, but:->
iproute2 _already_ depends on libmnl;-> (latest user being devlink).

cheers,
jamal