mariadb/storage/innobase/lock
Marko Mäkelä 01b44c054d MDEV-25026 Various code paths are accessing freed pages
The test case encryption.innodb_encrypt_freed was failing in
MemorySanitizer builds.

recv_recover_page(): Mark non-recovered pages as freed.

fil_crypt_rotate_page(): Before comparing the block->frame contents,
check if the block was marked as freed.

Other places: Whenever using BUF_GET_POSSIBLY_FREED, check the
block->page.status before accessing the page frame.

(Both uses of BUF_GET_IF_IN_POOL should be correct now.)
2021-03-02 11:51:22 +02:00
..
lock0iter.cc Merge 10.1 into 10.2 2019-05-13 17:54:04 +03:00
lock0lock.cc MDEV-25026 Various code paths are accessing freed pages 2021-03-02 11:51:22 +02:00
lock0prdt.cc MDEV-23719: Make lock_sys use page_id_t 2020-09-17 14:08:41 +03:00
lock0wait.cc MDEV-16264 fixup: Remove unused code and data 2020-09-30 14:28:11 +03:00