mirror of
https://github.com/MariaDB/server.git
synced 2025-02-01 11:31:51 +01:00
ed7e4b68ed
Problem was that crypt_data->min_key_version is not a reliable way
to detect is tablespace encrypted and could lead that in first page
of the second (page 192 and similarly for other files if more configured)
system tablespace file used key_version is replaced with zero leading
a corruption as in next startup page is though to be corrupted.
Note that crypt_data->min_key_version is updated only after all
pages from tablespace have been processed (i.e. key rotation is done)
and flushed.
fil_write_flushed_lsn
Use crypt_data->should_encrypt() instead.
|
||
|---|---|---|
| .. | ||
| fil0crypt.cc | ||
| fil0fil.cc | ||
| fil0pagecompress.cc | ||