Back to bug 1312274
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Ondrej Vasik | 2016-02-26 10:43:43 UTC | CC | ovasik | |
| Jakub Dorňák | 2016-02-26 11:11:07 UTC | Status | NEW | MODIFIED |
| errata-xmlrpc | 2016-02-26 11:20:29 UTC | Status | MODIFIED | ON_QA |
| Karel Volný | 2016-03-08 15:18:14 UTC | CC | kvolny | |
| Flags | needinfo?(jdornak) | |||
| Jakub Dorňák | 2016-03-08 16:58:23 UTC | Flags | needinfo?(jdornak) | |
| Karel Volný | 2016-03-09 14:49:45 UTC | Status | ON_QA | VERIFIED |
| Honza Horak | 2016-03-09 15:12:17 UTC | Depends On | 1289986 | |
| Jakub Dorňák | 2016-03-10 10:13:42 UTC | Doc Text | Cause: Unresolved concurrent acces to shared resource in function rotate_relay_log. Consequence: Segmentation fault Fix: Mutex lock on the resource used during rotate_relay_log call. Result: Segmentation fault doesn't happen in rotate_relay_log. |
|
| Lenka Špačková | 2016-03-18 09:27:36 UTC | Doc Text | Cause: Unresolved concurrent acces to shared resource in function rotate_relay_log. Consequence: Segmentation fault Fix: Mutex lock on the resource used during rotate_relay_log call. Result: Segmentation fault doesn't happen in rotate_relay_log. | Previously, when the rotate_relay_log() function was called, an unresolved concurrent access to a shared resource occurred. As a consequence, MySQL terminated unexpectedly with a segmentation fault. To fix this bug, a mutex lock on the resource is now used during the rotate_relay_log() call, and MySQL no longer crashes in this scenario. |
| errata-xmlrpc | 2016-03-22 00:38:08 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2016-03-22 15:49:13 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2016-03-22 11:49:13 UTC |
Back to bug 1312274