Thread (1 message) 1 message, 1 author, 2017-04-13

Re: [PATCH 1/5] netlink: extended ACK reporting

From: Joe Stringer <hidden>
Date: 2017-04-13 21:44:21

On 13/04/2017 12:24, "Johannes Berg" [off-list ref] wrote:
On Thu, 2017-04-13 at 16:05 +0200, Nicolas Dichtel wrote:
quoted
Sure. It was just to mention that attribute 0 exists somewhere.
The other 0 attribute is OVS_TUNNEL_KEY_ATTR_ID.
That looks like some really awkward hand-grown parsing - with all these
"struct ovs_len_tbl" looking almost like a policy, but not using that
code?

Seems like something somebody should take a hard look at and see if it
can't use more standard infrastructure.
I think that OVS was doing some more elaborate validation than most users,
so over time we picked up a bunch of extra parsing code that layers on top
of nla_parse(). I took a look at trying to broaden this and make it useful
to other users a while ago, but when I posted there wasn't much interest
from others on it so I just moved on. Maybe it's about time to pick that
back up.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help