On Fri, 2017-06-23 at 23:03 +0200, Arend van Spriel wrote: > > Also is this not a more fundamental flaw in netlink socket behavior. > Should there be some priority imposed on command responses over event > messages. Just seems like this patch is a workaround. In a way, but it's not that easy. ACK messages are really just that, messages, and having them bypass the queue might not be reasonable for the use case, having them be queued unconditionally would open an avenue for memory consumption attacks (send lots of dummy commands and let the ACKs accumulate), and deleting already "delivered" message could, I think, break semantics because I think delivery can be checked by the sender? Either way, I don't really see a good way to solve this problem in netlink. johannes
