sync_close destroys priority mutexes as regular ones
Bug #1295523 reported by
Laurynas Biveinis
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Percona Server moved to https://jira.percona.com/projects/PS |
Fix Released
|
Low
|
Laurynas Biveinis | ||
| 5.1 |
Invalid
|
Undecided
|
Unassigned | ||
| 5.5 |
Invalid
|
Undecided
|
Unassigned | ||
| 5.6 |
Fix Released
|
Low
|
Laurynas Biveinis | ||
Bug Description
Split off bug 1291202:
If sync_close encounters any priority mutexes on mutex_list, they are freed using the wrong overload. It is relatively benign, it only results in leaked high priority event and skipped high waiters flag equal to zero assertion.
The mutexes in question are buffer pool LRU and free list mutexes.
Related branches
lp:~laurynas-biveinis/percona-server/bug1295523
- Alexey Kopytov (community): Approve
-
Diff: 75 lines (+21/-2)2 files modifiedstorage/innobase/include/sync0sync.h (+1/-0)
storage/innobase/sync/sync0sync.cc (+20/-2)
| tags: | added: xtradb |
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #1 |
To post a comment you must log in.
Percona now uses JIRA for bug reports so this bug report is migrated to: https:/