netdev - Re: To netlink or not to netlink, that is the question

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: <CAHmME9oYtxL=sBpOquOjcqtQnYY=AFHC+OqMdeQD6X8HNoY4zw@mail.gmail.com>
Date:   Thu, 12 Jan 2017 21:07:43 +0100
From:   "Jason A. Donenfeld" <Jason@...c4.com>
To:     David Miller <davem@...emloft.net>
Cc:     Dan Williams <dcbw@...hat.com>,
        Stephen Hemminger <stephen@...workplumber.org>,
        Netdev <netdev@...r.kernel.org>
Subject: Re: To netlink or not to netlink, that is the question

On Thu, Jan 12, 2017 at 8:11 PM, David Miller <davem@...emloft.net> wrote:
> This is a fact of life, dumps are always chopped into suitable
> numbers of responses as necessary.  We do this for IPV4 routes,
> network interfaces, etc. and it all works out just fine.
>
> The thing you should be asking yourself is, if something as heavily
> used and fundamental as IPV4 can handle this, probably your scenerio
> can be handled just fine as well.

Okay, fair enough. I'll suck it up, then, and just use netlink in this
way. David - you concur with Stephen that ioctl is really not okay and
I should absolutely do netlink?