[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1491682394.2379.1.camel@sipsolutions.net>
Date: Sat, 08 Apr 2017 22:13:14 +0200
From: Johannes Berg <johannes@...solutions.net>
To: Jiri Pirko <jiri@...nulli.us>
Cc: linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
pablo@...filter.org, Jamal Hadi Salim <jhs@...atatu.com>,
Jiri Benc <jbenc@...hat.com>,
David Ahern <dsa@...ulusnetworks.com>
Subject: Re: [PATCH 1/5] netlink: extended ACK reporting
On Sat, 2017-04-08 at 20:40 +0200, Jiri Pirko wrote:
> > I think I'll leave it like this - if anyone really wants to say
> > "attribute 0 is missing" then we can add a flag later... The UAPI
> > does
> > take this into account by not including the attribute at all if the
> > data is invalid, so 0 in the userspace API can be done
>
> It a known issue, should be fixed right now. We are in no hurry. This
> waited +15 years to be done, no harm in couple more days.
It's not about any timing or anything - I simply think the likelihood
that this will be needed is zero, because almost no netlink family uses
attribute zero, those that do use it are older ones unlikely to be
updated to start with, and *then* needing to indicate that attribute 0
is missing? Not going to happen.
The extra code needed to handle this is therefore wasted.
> Also, could you please attach a patch to iproute2 for example which
> would make use of this. I just want to make sure it clicks.
No, I'm not going to do that. If you want it, please do it yourself.
I've done the testing on a slightly modified iw, but even there haven't
done any pretty-printing or parsing, just made sure the attributes show
up properly (by dumping them in hex).
johannes
Powered by blists - more mailing lists