You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bug#34930219 Missing synchronization of access to THD::m_protocol causing SIGSEGV
A stack allocated protocol instance was popped while i_s.processlist was
about to check whether the client connection was still alive. When the
protocol instance went out of scope, the call to connection_alive() accessed
an invalid pointer, causing SIGSEGV.
The fix is to cache the return value from the current protocol's
connection_alive() method when pushing, popping or getting the protocol.
This might leave results that are slightly out of sync with reality, but
a better synchronization is likely to cause performance degradation.
Change-Id: I3d512fadaa0df145af3f25d4cc03fa20143c5310
(cherry picked from commit 99c1919e0596bb6fe0292e602299e6da880fa352)
0 commit comments