Bug #110268 ibuf cursor restoration fails
Submitted: 3 Mar 2023 10:16 Modified: 3 Mar 2023 14:45
Reporter: Zeng Zihao Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S2 (Serious)
Version:8.0.25 OS:Linux
Assigned to: CPU Architecture:ARM

[3 Mar 2023 10:16] Zeng Zihao
Description:
2023-02-24T21:16:52.445604Z 0 [ERROR] [MY-012445] [InnoDB] ibuf cursor restoration fails!. ibuf record inserted to page 75:889
2023-02-24T21:16:52.445721Z 0 [ERROR] [MY-012446] [InnoDB] Submit a detailed bug report to http://bugs.mysql.com
PHYSICAL RECORD: n_fields 1; 1-byte offsets; info bits 0
 0: len 8; hex 696e66696d756d00; asc infimum ;;
PHYSICAL RECORD: n_fields 9; 1-byte offsets; info bits 32
 0: len 4; hex 0000004b; asc    K;;
 1: len 1; hex 00; asc  ;;
 2: len 4; hex 000003c4; asc     ;;
 3: len 30; hex 000001018603000480008601000100000dfe002800ff8603000400000800; asc                    (          ; (total 34 bytes);
 4: len 4; hex 8000081e; asc     ;;
 5: len 1; hex 80; asc  ;;
 6: len 10; hex 20202020202020202020; asc           ;;
 7: len 4; hex 80060125; asc    %;;
 8: len 6; hex 000000013be1; asc     ; ;;
DATA TUPLE: 3 fields;
 0: len 4; hex 0000004b; asc    K;;
 1: len 1; hex 00; asc  ;;
 2: len 4; hex 00000379; asc    y;;
PHYSICAL RECORD: n_fields 9; 1-byte offsets; info bits 32
 0: len 4; hex 0000004b; asc    K;;
 1: len 1; hex 00; asc  ;;
 2: len 4; hex 000003c4; asc     ;;
 3: len 30; hex 000001018603000480008601000100000dfe002800ff8603000400000800; asc                    (          ; (total 34 bytes);
 4: len 4; hex 8000081e; asc     ;;
 5: len 1; hex 80; asc  ;;
 6: len 10; hex 20202020202020202020; asc           ;;
 7: len 4; hex 80060125; asc    %;;
 8: len 6; hex 000000013be1; asc     ; ;;
2023-02-24T21:16:52.446117Z 0 [ERROR] [MY-012447] [InnoDB] [FATAL] Failed to restore ibuf position.
2023-02-24T21:16:52.446135Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: ut0ut.cc:548 thread 281472340052128
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
21:16:52 UTC - mysqld got signal 6 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x46000
/data/percona/sql/bin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x44) [0x2010b04]
/data/percona/sql/bin/mysqld(handle_fatal_signal+0x268) [0xe237b8]
linux-vdso.so.1(__kernel_rt_sigreturn+0) [0xffff85c047c0]
/usr/lib64/libc.so.6(gsignal+0xb0) [0xffff855d7470]
/usr/lib64/libc.so.6(abort+0x154) [0xffff855d881c]
/data/percona/sql/bin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x168) [0xa01334]
/data/percona/sql/bin/mysqld(ib::fatal::~fatal()+0xf4) [0x22d6914]
/data/percona/sql/bin/mysqld() [0x21b0b5c]
/data/percona/sql/bin/mysqld() [0x21aff28]
/data/percona/sql/bin/mysqld(ibuf_merge_or_delete_for_page(buf_block_t*, page_id_t, page_size_t const*, unsigned long)+0x628) [0xb3e868]
/data/percona/sql/bin/mysqld(buf_page_io_complete(buf_page_t*, bool)+0x1ec) [0xb9ba4c]
/data/percona/sql/bin/mysqld(fil_aio_wait(unsigned long)+0x1e8) [0xbb1c88]
/data/percona/sql/bin/mysqld() [0xb79c7c]
/data/percona/sql/bin/mysqld(std::thread::_State_impl<std::thread::_Invoker<std::tuple<Runnable, void (*)(unsigned long), unsigned long> > >::_M_run()+0x5c) [0x2296b4c]
/data/percona/sql/lib/libstdc++.so.6(+0xc9c0c) [0xffff858d5c0c]
/usr/lib64/libpthread.so.0(+0x87ac) [0xffff85ba97ac]
/usr/lib64/libc.so.6(+0xd547c) [0xffff8567647c]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
Writing a core file

How to repeat:
It happens randomly. I have not found a scenario where this problem can be reproduced stably.
[3 Mar 2023 14:45] MySQL Verification Team
Hi Mr. Zihao,

Thank you for your bug report.

It seems that you are not using our binary. We have noticed this types of queries in the binaries made by other parties , all which used wrong SSL version.

Hence, try to repeat this with our 8.0.32 official binary. If you succeed, you have to send us a fully repeatable test case in the form of the set of SQL commands that always lead to the exact same crash.

Can't repeat.