LOCK_thd_data and MYSQL_CALLBACK
Bug #1242748 reported by
Raghavendra D Prabhu
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS |
Fix Released
|
High
|
Sergei Glushchenko | ||
5.1 |
Invalid
|
Undecided
|
Unassigned | ||
5.5 |
Invalid
|
Undecided
|
Unassigned | ||
5.6 |
Fix Released
|
High
|
Sergei Glushchenko |
Bug Description
In 5.6 PS code, mysqld.cc:
mysql_
MYSQL_
However, in mysql-56, mysql-55 and PS-55, the order is
MYSQL_
mysql_
So, the order of locking is reversed there (though it may/not
matter depending on what is done in post_kill_
This needs to be resolved in either 5.6 PS or 5.5 PS.
Related branches
lp:~sergei.glushchenko/percona-server/5.6-ps-bug1242748
- Laurynas Biveinis (community): Approve
-
Diff: 13 lines (+1/-1)1 file modifiedPercona-Server/sql/mysqld.cc (+1/-1)
tags: | added: merge-regression |
To post a comment you must log in.
This changed in 5.6 because 5.6 has different behavior on THD destroy which causes to memory corruption when thread released without LOCK_thd_data locked. On 5.5 it is not necessary. See https:/ /mariadb. atlassian. net/browse/ MDEV-4889 for details.