From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 198571] New: [af_netlink]missing wakeup while closing af_netlink socket
Date: Wed, 24 Jan 2018 07:49:08 -0800 [thread overview]
Message-ID: <20180124074908.7e90b753@xeon-e3> (raw)
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.
reply other threads:[~2018-01-24 15:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180124074908.7e90b753@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.