Bug #42342 | Falcon crash in Index::duplicateKey | ||
---|---|---|---|
Submitted: | 26 Jan 2009 9:53 | Modified: | 7 May 2009 16:15 |
Reporter: | Philip Stoev | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Falcon storage engine | Severity: | S1 (Critical) |
Version: | 6.0-falcon-team | OS: | Any |
Assigned to: | Christopher Powers | CPU Architecture: | Any |
Tags: | F_RECORD TREE |
[26 Jan 2009 9:53]
Philip Stoev
[26 Jan 2009 14:35]
Kevin Lewis
Verified by code inspection. Unlike other places where Index::duplicateKey can be called, Table::update() does not get a shared lock on syncPrior first. So it is possible for a records to be scvenged and deleted while this function is traversing the prior record chain. It just so happens that Chris an I noticed this last Friday while discussing another issue. He made this change on Saturday which includes this fix as well. http://lists.mysql.com/commits/63991
[26 Jan 2009 17:37]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/64059 2975 Christopher Powers 2009-01-26 Bug #42342, "Falcon crash in Index::duplicateKey" Protect record version chain while searching for duplicate keys.
[13 Feb 2009 7:25]
Bugs System
Pushed into 6.0.10-alpha (revid:alik@sun.com-20090211182317-uagkyj01fk30p1f8) (version source revid:vvaintroub@mysql.com-20090126231319-7b6yu4zqp2xfxuqg) (merge vers: 6.0.10-alpha) (pib:6)
[7 May 2009 16:15]
MC Brown
Internal/test fix. No changelog entry required.