mariadb/storage/innobase/log
Thirunarayanan Balathandayuthapani 4dcd2d8513 MDEV-37412 Corrupted page during recovery aborts the server
Problem:
=======
When InnoDB encounters a corrupted page during crash recovery,
server would abort due to improper handling of page locks
and space references. The recovery process was not properly
cleaning up resources when corruption was detected,
leading to inconsistent state and server termination.

Solution:
=========
recover_low(): Move page lock recursive acquisition
after deferred/non-deferred page creation logic to
ensure consistent locking behavior for both code paths.
Ensure proper block recursive unlock for non-deferred tablespaces

recv_recover_page(): Simplify corrupted page cleanup by
removing redundant space reference handling.
2025-09-10 15:25:58 +03:00
..
log0crypt.cc Merge 10.5 into 10.6 2021-06-23 09:24:32 +03:00
log0log.cc MDEV-35171 OS_FILE_NORMAL and OS_FILE_AIO are misleading 2024-10-21 15:31:32 +02:00
log0recv.cc MDEV-37412 Corrupted page during recovery aborts the server 2025-09-10 15:25:58 +03:00
log0sync.cc Fixed compiler error with framesize=16384 in InnoDB log0sync.cc 2025-07-27 16:35:12 +03:00
log0sync.h MDEV-26789 log_write_up_to needs mechanism to prevent stalls of async. waiters 2021-10-08 13:18:59 +02:00