[TS-3597] TLS can fail accept / handshake since commit 2a8bb593fd

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 5.3.1, 6.0.0
• Component/s: SSL
• Assignee: Susan Hinrichs
• Reporter: Leif Hedstrom
• Created: 13/May/15 05:12
• Updated: 04/Feb/16 18:55
• Resolved: 15/May/15 15:58

Description

At least under certain conditions (slightly unclear,but possible a race with multiple NUMA nodes), we fail to accept / TLS handshake. I've tracked this down to the commit from 2a8bb593fdd7ca9125efad76e27f3f17f5bca794.

The commit prior to this does not expose the problem. gancho also discovered that this problem is only triggered when accept thread is off (0).

Also from gancho, when this reproduces, a command like e.g. this will fail the handshake completely (no ciphers):

openssl s_client -connect 10.1.2.3:443 -tls1 -servername some.host.com

Also, since this only happens with accept thread off (0), which implies accept on every ET_NET thread, maybe there's some sort of race condition going on here? That's just a wild speculation though.

Issue Links

• is related to: TS-3603 Debug Assert occurs in UnixNetVConnection::set_enabled when accept_threads are disabled