[MDEV-31534] Wrong value assigned to session_track_system_variables causes signal 11 crash Created: 2023-06-25  Updated: 2023-06-27  Resolved: 2023-06-26

Status: Closed
Project: MariaDB Server
Component/s: Server
Affects Version/s: 10.6.5, 10.4.30, 11.2.0
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: KedarV Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Environment:

Ubuntu 20, CentOS 7


Issue Links:
Duplicate
duplicates MDEV-25237 crash after setting global session_tr... Closed

 Description   

Setting session_track_system_variables to our of range value causes a crash upon new connection.

            MariaDB [(none)]> set global session_track_system_variables=crash_is_inevitable;
            ERROR 1193 (HY000): Unknown system variable 'crash_is_inevitable'
            MariaDB [(none)]> exit;
            ...
            root@ip-172-31-92-119:~# mysql
            mysql: Deprecated program name. It will be removed in a future release, use '/usr/bin/mariadb' instead
            ERROR 2013 (HY000): Lost connection to server at 'handshake: reading initial communication packet', system error: 11

Error log

- stack trace
            Thread pointer: 0x7f923c000fb8
            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 = 0x7f92404f7dd8 thread_stack 0x49000
            /usr/sbin/mysqld(my_print_stacktrace+0x32)[0x556cf07df252]
            /usr/sbin/mysqld(handle_fatal_signal+0x55d)[0x556cf027276d]
            /lib/x86_64-linux-gnu/libpthread.so.0(+0x14420)[0x7f924c924420]
            /lib/x86_64-linux-gnu/libc.so.6(+0x1886e5)[0x7f924c56d6e5]
            /usr/sbin/mysqld(my_strdup+0x1d)[0x556cf07db72d]
            /usr/sbin/mysqld(_ZN23Session_sysvars_tracker4initEP3THD+0x28)[0x556ceffaac38]
            /usr/sbin/mysqld(_Z18plugin_thdvar_initP3THD+0x1d2)[0x556cf0076512]
            /usr/sbin/mysqld(_ZN3THD4initEv+0x30)[0x556cf0016c90]
            /usr/sbin/mysqld(_ZN3THD11change_userEv+0x7c)[0x556cf001707c]
            /usr/sbin/mysqld(_ZN3THD15reset_for_reuseEv+0x1e)[0x556cf00171fe]
            /usr/sbin/mysqld(_ZN7CONNECT10create_thdEP3THD+0x28)[0x556cf01686e8]
            /usr/sbin/mysqld(_Z29one_thread_per_connection_endP3THDb+0x29d)[0x556ceff9532d]
            /usr/sbin/mysqld(_Z24do_handle_one_connectionP7CONNECT+0x16b)[0x556cf0168a4b]
            /usr/sbin/mysqld(handle_one_connection+0x3f)[0x556cf0168c2f]
            /lib/x86_64-linux-gnu/libpthread.so.0(+0x8609)[0x7f924c918609]
            /lib/x86_64-linux-gnu/libc.so.6(clone+0x43)[0x7f924c504133]
 
            Trying to get some variables.
            Some pointers may be invalid and cause the dump to abort.
            Query (0x0): (null)
            Connection ID (thread ID): 1274
            Status: NOT_KILLED



 Comments   
Comment by Alice Sherepa [ 2023-06-26 ]

Thank you for the report! This is the same problem as in MDEV-25237

Generated at Thu Feb 08 10:24:35 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.