netdev - Re: [PATCH net-next 0/2] Ease nsid allocation

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: <30d50c1d-d4c8-f339-816b-eb28ec4c0154@6wind.com>
Date:   Wed, 2 Oct 2019 10:46:03 +0200
From:   Nicolas Dichtel <nicolas.dichtel@...nd.com>
To:     David Miller <davem@...emloft.net>
Cc:     netdev@...r.kernel.org
Subject: Re: [PATCH net-next 0/2] Ease nsid allocation

Le 02/10/2019 à 03:20, David Miller a écrit :
> From: Nicolas Dichtel <nicolas.dichtel@...nd.com>
> Date: Mon, 30 Sep 2019 18:02:12 +0200
> 
>> The goal of the series is to ease nsid allocation from userland.
>> The first patch is a preparation work and the second enables to receive the
>> new nsid in the answer to RTM_NEWNSID.
> 
> The new reply message could break existing apps.
> 
> If an app only performs netnsid operations, and fills up the receive
> queue because it isn't reading these new replies (it had no reason to,
> they didn't exist previously), operations will start failing that
> would not fail previously because the receive queue is full.
Yes I see the problem. I was wondering if this was acceptable because the nl ack
is sent at the end. But nl ack are optional :/

> 
> Given this, I don't see how we can make the change.
> 
Is a new flag attribute ok to turn on this reply?


Thank you,
Nicolas