Commit 13109514 authored by Jon Olav Hauglid's avatar Jon Olav Hauglid

Bug #55223 assert in Protocol::end_statement during CREATE DATABASE

The problem was that a statement could cause an assert if it was aborted by
KILL QUERY while it waited on a metadata lock. This assert checks that a
statement either sends OK or an error to the client. If the bug was triggered
on release builds, it caused OK to be sent to the client instead of
ER_QUERY_INTERRUPTED.

The root cause of the problem was that there are two separate ways to tell if a
statement is killed: thd->killed and mysys_var->abort. KILL QUERY causes both
to be set, thd->killed before mysys_var->abort. Also, both values are reset
at the end of statement execution. This means that it is possible for
KILL QUERY to first set thd->killed, then have the killed statement reset
both thd->killed and mysys_var->abort and finally have KILL QUERY set
mysys_var->abort. This means that the connection with the killed statement
will start executing the next statement with the two values out of sync - i.e.
thd->killed not set but mysys_var->abort set.

Since mysys_var->abort is used to check if a wait for a metadata lock should
be aborted, the next statement would immediately abort any such waiting.
When waiting is aborted, no OK message is sent and thd->killed is checked to
see if ER_QUERY_INTERRUPTED should be sent to the client. But since
the->killed had been reset, neither OK nor an error message was sent to the
client. This then triggered the assert.

This patch fixes the problem by changing the metadata lock waiting code to
check thd->killed.

No test case added as reproducing the assert is dependent on very exact timing
of two (or more) threads. The patch has been checked using RQG and the grammar
posted on the bug report.
parent 52b1e11e
...@@ -881,67 +881,6 @@ uint MDL_ticket::get_deadlock_weight() const ...@@ -881,67 +881,6 @@ uint MDL_ticket::get_deadlock_weight() const
} }
/**
Helper functions and macros to be used for killable waiting in metadata
locking subsystem.
@sa THD::enter_cond()/exit_cond()/killed.
@note We can't use THD::enter_cond()/exit_cond()/killed directly here
since this will make metadata subsystem dependent on THD class
and thus prevent us from writing unit tests for it. And usage of
wrapper functions to access THD::killed/enter_cond()/exit_cond()
will probably introduce too much overhead.
*/
#define MDL_ENTER_COND(A, B, C, D) \
mdl_enter_cond(A, B, C, D, __func__, __FILE__, __LINE__)
static inline const char *mdl_enter_cond(THD *thd,
st_my_thread_var *mysys_var,
mysql_cond_t *cond,
mysql_mutex_t *mutex,
const char *calling_func,
const char *calling_file,
const unsigned int calling_line)
{
mysql_mutex_assert_owner(mutex);
mysys_var->current_mutex= mutex;
mysys_var->current_cond= cond;
DEBUG_SYNC(thd, "mdl_enter_cond");
return set_thd_proc_info(thd, "Waiting for table",
calling_func, calling_file, calling_line);
}
#define MDL_EXIT_COND(A, B, C, D) \
mdl_exit_cond(A, B, C, D, __func__, __FILE__, __LINE__)
static inline void mdl_exit_cond(THD *thd,
st_my_thread_var *mysys_var,
mysql_mutex_t *mutex,
const char* old_msg,
const char *calling_func,
const char *calling_file,
const unsigned int calling_line)
{
DBUG_ASSERT(mutex == mysys_var->current_mutex);
mysql_mutex_unlock(mutex);
mysql_mutex_lock(&mysys_var->mutex);
mysys_var->current_mutex= NULL;
mysys_var->current_cond= NULL;
mysql_mutex_unlock(&mysys_var->mutex);
DEBUG_SYNC(thd, "mdl_exit_cond");
(void) set_thd_proc_info(thd, old_msg, calling_func,
calling_file, calling_line);
}
/** Construct an empty wait slot. */ /** Construct an empty wait slot. */
MDL_wait::MDL_wait() MDL_wait::MDL_wait()
...@@ -1021,15 +960,14 @@ MDL_wait::timed_wait(THD *thd, struct timespec *abs_timeout, ...@@ -1021,15 +960,14 @@ MDL_wait::timed_wait(THD *thd, struct timespec *abs_timeout,
{ {
const char *old_msg; const char *old_msg;
enum_wait_status result; enum_wait_status result;
st_my_thread_var *mysys_var= my_thread_var;
int wait_result= 0; int wait_result= 0;
mysql_mutex_lock(&m_LOCK_wait_status); mysql_mutex_lock(&m_LOCK_wait_status);
old_msg= MDL_ENTER_COND(thd, mysys_var, &m_COND_wait_status, old_msg= thd_enter_cond(thd, &m_COND_wait_status, &m_LOCK_wait_status,
&m_LOCK_wait_status); "Waiting for table");
while (!m_wait_status && !mysys_var->abort && while (!m_wait_status && !thd_killed(thd) &&
wait_result != ETIMEDOUT && wait_result != ETIME) wait_result != ETIMEDOUT && wait_result != ETIME)
wait_result= mysql_cond_timedwait(&m_COND_wait_status, &m_LOCK_wait_status, wait_result= mysql_cond_timedwait(&m_COND_wait_status, &m_LOCK_wait_status,
abs_timeout); abs_timeout);
...@@ -1048,14 +986,14 @@ MDL_wait::timed_wait(THD *thd, struct timespec *abs_timeout, ...@@ -1048,14 +986,14 @@ MDL_wait::timed_wait(THD *thd, struct timespec *abs_timeout,
false, which means that the caller intends to restart the false, which means that the caller intends to restart the
wait. wait.
*/ */
if (mysys_var->abort) if (thd_killed(thd))
m_wait_status= KILLED; m_wait_status= KILLED;
else if (set_status_on_timeout) else if (set_status_on_timeout)
m_wait_status= TIMEOUT; m_wait_status= TIMEOUT;
} }
result= m_wait_status; result= m_wait_status;
MDL_EXIT_COND(thd, mysys_var, &m_LOCK_wait_status, old_msg); thd_exit_cond(thd, old_msg);
return result; return result;
} }
......
...@@ -721,10 +721,10 @@ void mdl_destroy(); ...@@ -721,10 +721,10 @@ void mdl_destroy();
extern bool mysql_notify_thread_having_shared_lock(THD *thd, THD *in_use, extern bool mysql_notify_thread_having_shared_lock(THD *thd, THD *in_use,
bool needs_thr_lock_abort); bool needs_thr_lock_abort);
extern "C" const char *set_thd_proc_info(void *thd_arg, const char *info, extern "C" const char* thd_enter_cond(MYSQL_THD thd, mysql_cond_t *cond,
const char *calling_function, mysql_mutex_t *mutex, const char *msg);
const char *calling_file, extern "C" void thd_exit_cond(MYSQL_THD thd, const char *old_msg);
const unsigned int calling_line);
#ifndef DBUG_OFF #ifndef DBUG_OFF
extern mysql_mutex_t LOCK_open; extern mysql_mutex_t LOCK_open;
#endif #endif
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment