Thread (16 messages) 16 messages, 4 authors, 2019-10-10

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

From: Nicolas Dichtel <hidden>
Date: 2019-10-02 08:46:09

Le 02/10/2019 à 03:20, David Miller a écrit :
From: Nicolas Dichtel <redacted>
Date: Mon, 30 Sep 2019 18:02:12 +0200
quoted
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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help