Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.1(EOL), 10.2(EOL)
Description
MDEV-11759 added a tablespace lookup to PageConverter::validate(), based on the contents of the page. This does not seem to make any sense. When InnoDB is importing a tablespace, the tablespace ID that is being used in the file may or may not be in use by existing tables in the server instance. If the ID is not used, the lookup would always return NULL. If a tablespace by that ID happens to exist, then we could be in deep trouble, because we are invoking buf_page_is_corrupted() with a completely bogus tablespace.
Please add a proper IMPORT test for page_compression and encryption.
In 10.2, please remove the function fil_space_found_by_id() altogether. Like fil_space_get(), it is unsafe to use, because the pointer can be stale if the tablespace was dropped just after the call.
Attachments
Issue Links
- is caused by
-
MDEV-11759 Encryption code in MariaDB 10.1/10.2 causes compatibility problems
- Closed
- is duplicated by
-
MDEV-12396 MariaDB Server SEGV crash when importing tablespace for a large table (4GB)
- Closed
- is part of
-
MDEV-12253 Buffer pool blocks are accessed after they have been freed
- Closed