XtraDB 1.1.8-26.0 assert crash under valgrind
Bug #1015109 reported by
Sergei Golubchik
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS |
Fix Released
|
High
|
Stewart Smith | ||
5.5 |
Fix Released
|
High
|
Stewart Smith |
Bug Description
in MariaDB tree, under valgrind, XtraDB crashes like this:
innodb.
...
mysqltest: At line 441: query 'DROP TABLE worklog5743_key2' failed: 2013: Lost connection to MySQL server during query
...
120616 6:25:30 InnoDB: Assertion failure in thread 67938640 in file buf0lru.c line 864
InnoDB: Failing assertion: mutex_own(
See, for example,
http://
InnoDB does not crash there.
This XtraDB code was introduced in the innodb_
Related branches
lp:~stewart/percona-server/5.5.27-plus-bugfixes
On hold
for merging
into
lp:percona-server/5.5
- Alexey Kopytov (community): Needs Information
- Laurynas Biveinis (community): Needs Information
-
Diff: 55 lines (+15/-6)1 file modifiedPercona-Server/storage/innobase/buf/buf0lru.c (+15/-6)
To post a comment you must log in.
It's a regression introduced in 5.5 when merging the upstream fix for http:// bugs.mysql. com/bug. php?id= 64284. The new code in buf_flush_ dirty_pages( ) locks the global buffer pool mutex rather than LRU_list_mutex.
This specific bug only applies to debug builds, because buf_LRU_ insert_ zip_clean( ) a UNIV_DEBUG-only function. But we should inspect all recently added calls to buf_pool_ mutex_enter( ) in general and the fix for #51325 in particular to verify if they are compatible with innodb_ split_buf_ pool_mutex. patch.