> On Thu, 2020-02-13 at 11:21 +0000, Sergey Matyukevich wrote:
> > >
> > > > Sure, I can fix hostapd instead. Could you point me at some good
> > > > starting point to look at ? Are there any user-space tools that
> > > > started to use strict validation ?
> > >
> > > It's not really opt-in or not, it's entirely a kernel choice.
> >
> > I mean, I don't know what userspace is supposed to do in the case,
> > when kernel is doing strict validation. So I was asking about any
> > pointers to docs or userspace tools that already do netlink
> > machinery appropriately.
>
> Userspace is just supposed to create well-formed messages :-)
>
> But ... it really is a kernel bug. The nl80211_policy is missing an
> entry for NL80211_ATTR_STATUS_CODE, so for *strict* commands, it's
> assumed to not be supported. Need to add something like
>
> [NL80211_ATTR_STATUS_CODE] = { .type = NLA_U16, },
>
> to the nl80211_policy, or perhaps with a range indicating that 0 isn't
> valid or something.
Great. Thanks for explanation. Would you mind if I send a fix ?
Or now you have your own plans for this ?
Regards,
Sergey
