diff options
| author | Gleb Shchepa <gshchepa@mysql.com> | 2009-12-01 14:24:44 +0400 |
|---|---|---|
| committer | Gleb Shchepa <gshchepa@mysql.com> | 2009-12-01 14:24:44 +0400 |
| commit | 4e3f4320b27b00ddd00df8ab70abe3ba74af1957 (patch) | |
| tree | 326fe24b2b926b4a517ae4575d6f28d1f34bca49 /storage | |
| parent | 8db5d495d408ed840fa29edc7f865db14ffb9d64 (diff) | |
| download | mariadb-git-4e3f4320b27b00ddd00df8ab70abe3ba74af1957.tar.gz | |
Bug #38883 (reopened): thd_security_context is not thread safe, crashes?
The bug 38816 changed the lock that protects THD::query from
LOCK_thread_count to LOCK_thd_data, but didn't update the associated
InnoDB functions.
1. The innobase_mysql_prepare_print_arbitrary_thd and the
innobase_mysql_end_print_arbitrary_thd InnoDB functions have been
removed, since now we have a per-thread mutex: now we don't need to wrap
several inter-thread access tries to THD::query with a single global
LOCK_thread_count lock, so we can simplify the code.
2. The innobase_mysql_print_thd function has been modified to lock
LOCK_thd_data in direct way.
Diffstat (limited to 'storage')
0 files changed, 0 insertions, 0 deletions