Forwarding this to netdev because group may have different opinions. IMHO netlink is a multicast communication mechanism and therefore not it does not have the close semantics of other connection oriented protocols. Therefore this is not a bug.
Begin forwarded message: Date: Wed, 24 Jan 2018 12:20:00 +0000 From: bugzilla-dae...@bugzilla.kernel.org To: step...@networkplumber.org Subject: [Bug 198571] New: [af_netlink]missing wakeup while closing af_netlink socket https://bugzilla.kernel.org/show_bug.cgi?id=198571 Bug ID: 198571 Summary: [af_netlink]missing wakeup while closing af_netlink socket Product: Networking Version: 2.5 Kernel Version: 2.6.32 Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Other Assignee: step...@networkplumber.org Reporter: yushou...@sina.com Regression: No In a multithread program, thread A wait for a message from a af_netlink socket with the interface select first. Then thread B calls close to this socket. In this situation, thread A would not be woken up forever. This problem may be caused by missing call to the funtion release_sock to the socket in the funthon netlink_release. Can anyone fix this problem? -- You are receiving this mail because: You are the assignee for the bug.
