From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stephen Hemminger <stephen@networkplumber.org>
Subject: Fw: [Bug 198571] New: [af_netlink]missing wakeup while closing
 af_netlink socket
Date: Wed, 24 Jan 2018 07:49:08 -0800
Message-ID: <20180124074908.7e90b753@xeon-e3>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
To: netdev@vger.kernel.org
Return-path: <netdev-owner@vger.kernel.org>
Received: from mail-pf0-f170.google.com ([209.85.192.170]:38943 "EHLO
        mail-pf0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S934124AbeAXPtL (ORCPT
        <rfc822;netdev@vger.kernel.org>); Wed, 24 Jan 2018 10:49:11 -0500
Received: by mail-pf0-f170.google.com with SMTP id e11so3362842pff.6
        for <netdev@vger.kernel.org>; Wed, 24 Jan 2018 07:49:11 -0800 (PST)
Received: from xeon-e3 (204-195-18-133.wavecable.com. [204.195.18.133])
        by smtp.gmail.com with ESMTPSA id v4sm1103070pgq.23.2018.01.24.07.49.10
        for <netdev@vger.kernel.org>
        (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
        Wed, 24 Jan 2018 07:49:10 -0800 (PST)
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

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@bugzilla.kernel.org
To: stephen@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: stephen@networkplumber.org
          Reporter: yushouhua@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.