mariadb/storage/innobase
Marko Mäkelä 53c6c823dc MDEV-33464 Crash when innodb_max_undo_log_size is set to innodb_page_size*4294967296
purge_sys_t::truncating_tablespace(): Clamp the
innodb_max_undo_log_size to the maximum number of pages
before converting the result into a 32-bit unsigned integer.

This fixes up commit f8c88d905b (MDEV-33213).

In later major versions, we would use 32-bit unsigned integer here
due to commit ca501ffb04
and the code would crash also on 64-bit processors.

Reviewed by: Debarun Banerjee
2024-02-15 12:34:04 +02:00
..
btr
buf
data
dict
eval
fil
fsp
fts
fut
gis
ha
handler
ibuf
include
lock
log
mem
mtr
mysql-test/storage_engine
os
page
pars
que
read
rem
row
srv
sync
trx MDEV-33464 Crash when innodb_max_undo_log_size is set to innodb_page_size*4294967296 2024-02-15 12:34:04 +02:00
unittest
ut
.clang-format-old
bzip2.cmake
CMakeLists.txt
COPYING.Google
COPYING.Percona
lz4.cmake
lzma.cmake
lzo.cmake
snappy.cmake