1
0
mirror of https://github.com/MariaDB/server.git synced 2025-08-27 13:04:36 +03:00
Files
mariadb/mysql-test/extra/rpl_tests
Sujatha 836d708997 MDEV-22451: SIGSEGV in __memmove_avx_unaligned_erms/memcpy from _my_b_write on CREATE after RESET MASTER
Analysis:
========
RESET MASTER TO # command deletes all binary log files listed in the index
file, resets the binary log index file to be empty, and creates a new binary
log with number #. When the user provided binary log number is greater than
the max allowed value '2147483647' server fails to generate a new binary log.
The RESET MASTER statement marks the binlog closure status as
'LOG_CLOSE_TO_BE_OPENED' and exits. Statements which follow RESET MASTER
try to write to binary log they find the log_state != LOG_CLOSED and
proceed to write to binary log cache and it results in crash.

Fix:
===
During MYSQL_BIN_LOG open, if generation of new binary log name fails then the
"log_state" needs to be marked as "LOG_CLOSED". With this further statements
will find binary log as closed and they will skip writing to the binary log.
2020-05-20 17:42:28 +05:30
..
2012-09-27 20:09:46 +02:00
2017-09-21 22:02:21 +02:00
2014-02-03 15:22:39 +01:00
2017-09-21 22:02:21 +02:00
2017-09-21 22:02:21 +02:00
2014-01-22 15:29:36 +01:00
2011-01-13 12:21:57 +00:00
2016-12-05 20:19:01 +02:00
2012-03-28 01:04:46 +02:00
2014-01-29 15:41:10 +02:00
2017-09-21 22:02:21 +02:00