| Bug #36579 | Dumping information about locks in use may lead to a server crash | ||
|---|---|---|---|
| Submitted: | 7 May 2008 22:37 | Modified: | 2 Sep 2008 18:24 |
| Reporter: | Davi Arnaut (OCA) | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server | Severity: | S2 (Serious) |
| Version: | 5.0, 5.1, 6.0 BK | OS: | Any |
| Assigned to: | Davi Arnaut | CPU Architecture: | Any |
[7 May 2008 22:37]
Davi Arnaut
[10 Jun 2008 12:39]
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/47680 2649 Davi Arnaut 2008-06-10 Bug#36579 Dumping information about locks in use may lead to a server crash Dumping information about locks in use by sending a SIGHUP signal to the server or by invoking the "mysqladmin debug" command may lead to a server crash in debug builds or to undefined behavior in production builds. The problem was that a mutex that protects a lock object (THR_LOCK) might have been destroyed before the lock object was actually removed from the list of locks in use, causing a race condition with other threads iterating over the list. The solution is to destroy the mutex only after removing lock object from the list.
[10 Jun 2008 12:44]
Davi Arnaut
Queued to 6.0-runtime
[25 Aug 2008 11:04]
Georgi Kodinov
Moving back to "Patch Approved" pending push into 5.0 and 5.1
[25 Aug 2008 13:19]
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/52455 2673 Davi Arnaut 2008-08-25 Bug#36579 Dumping information about locks in use may lead to a server crash Dumping information about locks in use by sending a SIGHUP signal to the server or by invoking the "mysqladmin debug" command may lead to a server crash in debug builds or to undefined behavior in production builds. The problem was that a mutex that protects a lock object (THR_LOCK) might have been destroyed before the lock object was actually removed from the list of locks in use, causing a race condition with other threads iterating over the list. The solution is to destroy the mutex only after removing lock object from the list.
[25 Aug 2008 13:29]
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/52457 2673 Davi Arnaut 2008-08-25 Bug#36579 Dumping information about locks in use may lead to a server crash Dumping information about locks in use by sending a SIGHUP signal to the server or by invoking the "mysqladmin debug" command may lead to a server crash in debug builds or to undefined behavior in production builds. The problem was that a mutex that protects a lock object (THR_LOCK) might have been destroyed before the lock object was actually removed from the list of locks in use, causing a race condition with other threads iterating over the list. The solution is to destroy the mutex only after removing lock object from the list.
[25 Aug 2008 13:31]
Davi Arnaut
Queued to 5.0-bugteam
[25 Aug 2008 13:58]
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/52461 2720 Davi Arnaut 2008-08-25 [merge] Merge Bug#36579 into mysql-5.1-bugteam
[25 Aug 2008 14:01]
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/52462 2720 Davi Arnaut 2008-08-25 [merge] Merge Bug#36579 into mysql-5.1-bugteam
[26 Aug 2008 18:33]
Bugs System
Pushed into 5.0.70 (revid:davi.arnaut@sun.com-20080825131852-tdrxno3w50u91hq8) (version source revid:davi.arnaut@sun.com-20080826182704-ikgad9sf3142e7x9) (pib:3)
[26 Aug 2008 19:15]
Bugs System
Pushed into 5.1.28 (revid:davi.arnaut@sun.com-20080825135734-5gigojaj64ojnb2f) (version source revid:davi.arnaut@sun.com-20080826183817-r22ie0hgagpcn6su) (pib:3)
[26 Aug 2008 20:06]
Paul DuBois
Noted in 5.0.70, 5.1.28 changelogs. Dumping information about locks in use by sending a SIGHUP signal to the server or by invoking the mysqladmin debug command could lead to a server crash in debug builds or to undefined behavior in production builds. Setting report to NDI pending push into 6.0.x.
[2 Sep 2008 18:24]
Paul DuBois
Noted in 6.0.6 changelog.
[13 Sep 2008 22:21]
Bugs System
Pushed into 6.0.6-alpha (revid:davi.arnaut@sun.com-20080825135734-5gigojaj64ojnb2f) (version source revid:hakan@mysql.com-20080716105246-eg0utbybp122n2w9) (pib:3)
