summaryrefslogtreecommitdiff
path: root/Docs/glibc-2.2.5.patch
diff options
context:
space:
mode:
authorGleb Shchepa <gshchepa@mysql.com>2009-07-24 20:58:58 +0500
committerGleb Shchepa <gshchepa@mysql.com>2009-07-24 20:58:58 +0500
commit6aea4cebfc2eb6d39ccfe4f7fc53ac0dd1fc9ac5 (patch)
tree09d21c8df0aaa2410de0d4420236458edc9d4022 /Docs/glibc-2.2.5.patch
parentec7ea4454102db998c5477624f576308e52d9f3d (diff)
downloadmariadb-git-6aea4cebfc2eb6d39ccfe4f7fc53ac0dd1fc9ac5.tar.gz
Bug #38816: kill + flush tables with read lock + stored
procedures causes crashes! The problem of that bugreport was mostly fixed by the patch for bug 38691. However, attached test case focused on another crash or valgrind warning problem: SHOW PROCESSLIST query accesses freed memory of SP instruction that run in a parallel connection. Changes of thd->query/thd->query_length in dangerous places have been guarded with the per-thread LOCK_thd_data mutex (the THD::LOCK_delete mutex has been renamed to THD::LOCK_thd_data).
Diffstat (limited to 'Docs/glibc-2.2.5.patch')
0 files changed, 0 insertions, 0 deletions