Bug #22053 | REPAIR table can crash server for some really damaged MyISAM tables | ||
---|---|---|---|
Submitted: | 6 Sep 2006 15:20 | Modified: | 3 Jan 2007 11:07 |
Reporter: | Valeriy Kravchuk | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: MyISAM storage engine | Severity: | S1 (Critical) |
Version: | 5.0.25-BK, 5.0.24a, 5.1.11 | OS: | Linux (Linux) |
Assigned to: | Sergey Vojtovich | CPU Architecture: | Any |
[6 Sep 2006 15:20]
Valeriy Kravchuk
[27 Sep 2006 0:40]
Trudy Pelzer
This problem may be related to bug#22562.
[13 Oct 2006 10:10]
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/13649 ChangeSet@1.2530, 2006-10-13 15:10:14+05:00, svoj@may.pils.ru +1 -0 BUG#22053 - REPAIR table can crash server for some really damaged MyISAM tables When unpacking a blob column from broken row server crash could happen. This could rather happen when trying to repair a table using either REPAIR TABLE or myisamchk, though it also could happend when trying to access broken row using other SQL statements like SELECT if table is not marked as crashed. Fixed ulong overflow when trying to extract blob from broken row. Affects MyISAM only. No test case, since it needs broken myisam table.
[27 Dec 2006 0:15]
Antony Curtis
Pushed to 5.1.15-beta repository
[27 Dec 2006 2:27]
Antony Curtis
Pushed to 5.0.34 repository
[27 Dec 2006 10:01]
Antony Curtis
Pushed to 4.1.23 repository
[3 Jan 2007 11:07]
Jon Stephens
Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release. If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at http://dev.mysql.com/doc/en/installing-source.html Documented bugfix in 4.1.23, 5.0.34, and 5.1.15 changelogs.