On Fri, 2017-06-23 at 23:03 +0200, Arend van Spriel wrote: > On 23-06-17 11:26, Luca Coelho wrote: > > From: Andrei Otcheretianski <andrei.otcheretianski@xxxxxxxxx> > > > > If NAN interface is created with NL80211_ATTR_SOCKET_OWNER, the socket > > that is used to create the interface is used for all NAN operations and > > reporting NAN events. > > However, it turns out that sending commands and receiving events on > > the same socket is not possible in a completely race-free way: > > If the socket buffer is overflowed by the events, the command response > > will not be sent. In that case the caller will block forever on recv. > > Using non-blocking socket for commands is more complicated and still > > the command response or ack may not be received. > > So, keep unicasting NAN events to the interface creator, but allow > > using a different socket for commands. > > Sounds like this patch is missing significant changes in the > documentation of nl80211 API: Thanks Arend! Andrei is going to fix the documentation and I'll send v2. -- Luca.
