[MDEV-21513] Fix some crashes in ALTER TABLE…IMPORT TABLESPACE Created: 2020-01-17  Updated: 2020-01-17  Resolved: 2020-01-17

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.0, 10.1, 10.2, 10.3, 10.4, 10.5
Fix Version/s: 10.2.31, 10.3.22, 10.4.12, 10.5.1

Type: Bug Priority: Major
Reporter: Marko Mäkelä Assignee: Marko Mäkelä
Resolution: Fixed Votes: 0
Labels: corruption

Issue Links:
Blocks
blocks MDEV-20931 ALTER...IMPORT can crash the server Closed
blocks MDEV-21499 Merge new release of InnoDB 5.7.29 to... Closed
Relates
relates to MDEV-13542 Crashing on a corrupted page is unhel... Closed

 Description   

MySQL 5.7.29 includes a fix for avoiding some crashes in IndexPurge::next() in ALTER TABLE…IMPORT TABLESPACE:
Bug#29454828 ASSERTION ON IMPORT VIA TRANSPORTABLE TABLESPACE
The test case introduces some fault injection that does not appear to cover the changed functionality.

MariaDB should fix this in a better way, by replacing the btr_pcur_move_to_next_user_rec() call with equivalent code, and replacing the btr_pcur_move_to_next_page() call with code that will not kill the server, but return an error to the caller.
Ultimately, in MDEV-13542 we should make btr_pcur_move_to_next_user_rec() robust, and check the status in all callers.
Generated at Thu Feb 08 09:07:42 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.