summaryrefslogtreecommitdiffstats
path: root/net/bluetooth
diff options
context:
space:
mode:
authorGang He <ghe@suse.com>2018-05-02 17:28:35 +0200
committerDavid Teigland <teigland@redhat.com>2018-05-02 17:28:35 +0200
commitf706d830154b6c8405c6b77595a60d135182c97e (patch)
treeb09e5fa8f6c7df5b9da46888053358dba1f83c9e /net/bluetooth
parentdlm: fix a clerical error when set SCTP_NODELAY (diff)
downloadlinux-f706d830154b6c8405c6b77595a60d135182c97e.tar.xz
linux-f706d830154b6c8405c6b77595a60d135182c97e.zip
dlm: make sctp_connect_to_sock() return in specified time
When the user setup a two-ring cluster, DLM kernel module will automatically selects to use SCTP protocol to communicate between each node. There will be about 5 minute hang in DLM kernel module, in case one ring is broken before switching to another ring, this will potentially affect the dependent upper applications, e.g. ocfs2, gfs2, clvm and clustered-MD, etc. Unfortunately, if the user setup a two-ring cluster, we can not specify DLM communication protocol with TCP explicitly, since DLM kernel module only supports SCTP protocol for multiple ring cluster. Base on my investigation, the time is spent in sock->ops->connect() function before returns ETIMEDOUT(-110) error, since O_NONBLOCK argument in connect() function does not work here, then we should make sock->ops->connect() function return in specified time via setting socket SO_SNDTIMEO atrribute. Signed-off-by: Gang He <ghe@suse.com> Signed-off-by: David Teigland <teigland@redhat.com>
Diffstat (limited to 'net/bluetooth')
0 files changed, 0 insertions, 0 deletions