netdev - Fw: [Bug 198571] New: [af_netlink]missing wakeup while closing af

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20180124074908.7e90b753@xeon-e3>
Date:   Wed, 24 Jan 2018 07:49:08 -0800
From:   Stephen Hemminger <stephen@...workplumber.org>
To:     netdev@...r.kernel.org
Subject: Fw: [Bug 198571] New: [af_netlink]missing wakeup while closing
 af_netlink socket

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-daemon@...zilla.kernel.org
To: stephen@...workplumber.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: stephen@...workplumber.org
          Reporter: yushouhua@...a.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.