MySQL Bugs: #82386: handle_fatal_signal (sig=6) in fil_set_compression

Bug #82386	handle_fatal_signal (sig=6) in fil_set_compression \| innobase/fil/fil0fil.cc
Submitted:	30 Jul 2016 5:30	Modified:	1 Aug 2016 7:16
Reporter:	Ramesh Sivaraman	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server: InnoDB storage engine	Severity:	S3 (Non-critical)
Version:	5.7.10	OS:	CentOS
Assigned to:		CPU Architecture:	Any
Tags:	debug

Description:
GDB info

#0  0x00007f1b4a2c3741 in __pthread_kill (threadid=<optimized out>, signo=6) at ../nptl/sysdeps/unix/sysv/linux/pthread_kill.c:61
#1  0x00000000017ef51c in my_write_core (sig=6) at /sda/mysql-server_dbg/mysys/stacktrace.c:247
#2  0x0000000000e583e4 in handle_fatal_signal (sig=6) at /sda/mysql-server_dbg/sql/signal_handler.cc:220
#3  <signal handler called>
#4  0x00007f1b4844e5f7 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#5  0x00007f1b4844fce8 in __GI_abort () at abort.c:90
#6  0x0000000001b36ea3 in ut_dbg_assertion_failed (expr=0x0, file=0x2100218 "/sda/mysql-server_dbg/storage/innobase/fil/fil0fil.cc", line=6973) at /sda/mysql-server_dbg/storage/innobase/ut/ut0dbg.cc:67
#7  0x0000000001c24c49 in fil_set_compression (space_id=23, algorithm=0x7f1b09084840 "") at /sda/mysql-server_dbg/storage/innobase/fil/fil0fil.cc:6973
#8  0x00000000019118c3 in ha_innobase::open (this=0x7f1b09084c30, name=0x7f1b090369e8 "./test/t", mode=2, test_if_locked=2) at /sda/mysql-server_dbg/storage/innobase/handler/ha_innodb.cc:5839
#9  0x0000000000ed3057 in handler::ha_open (this=0x7f1b09084c30, table_arg=0x7f1b09059220, name=0x7f1b090369e8 "./test/t", mode=2, test_if_locked=2) at /sda/mysql-server_dbg/sql/handler.cc:2629
#10 0x00000000015cf44c in open_table_from_share (thd=0x7f1b09019000, share=0x7f1b09036630, alias=0x7f1b0902bb68 "t", db_stat=39, prgflag=8, ha_open_flags=0, outparam=0x7f1b09059220, is_create_table=false) at /sda/mysql-server_dbg/sql/table.cc:3300
#11 0x00000000014602a2 in open_table (thd=0x7f1b09019000, table_list=0x7f1b0902bb70, ot_ctx=0x7f1b4a8b9ea0) at /sda/mysql-server_dbg/sql/sql_base.cc:3454
#12 0x0000000001462b34 in open_and_process_table (thd=0x7f1b09019000, lex=0x7f1b0901b2e8, tables=0x7f1b0902bb70, counter=0x7f1b0901b3a8, flags=0, prelocking_strategy=0x7f1b4a8b9fa0, has_prelocking_list=false, ot_ctx=0x7f1b4a8b9ea0) at /sda/mysql-server_dbg/sql/sql_base.cc:5024
#13 0x0000000001463bd2 in open_tables (thd=0x7f1b09019000, start=0x7f1b4a8b9f60, counter=0x7f1b0901b3a8, flags=0, prelocking_strategy=0x7f1b4a8b9fa0) at /sda/mysql-server_dbg/sql/sql_base.cc:5633
#14 0x0000000001464e58 in open_tables_for_query (thd=0x7f1b09019000, tables=0x7f1b0902bb70, flags=0) at /sda/mysql-server_dbg/sql/sql_base.cc:6373
#15 0x00000000016e15c2 in Sql_cmd_insert::mysql_insert (this=0x7f1b0902c100, thd=0x7f1b09019000, table_list=0x7f1b0902bb70) at /sda/mysql-server_dbg/sql/sql_insert.cc:464
#16 0x00000000016e88f6 in Sql_cmd_insert::execute (this=0x7f1b0902c100, thd=0x7f1b09019000) at /sda/mysql-server_dbg/sql/sql_insert.cc:3082
#17 0x00000000014e5b7f in mysql_execute_command (thd=0x7f1b09019000, first_level=true) at /sda/mysql-server_dbg/sql/sql_parse.cc:3510
#18 0x00000000014eb3dd in mysql_parse (thd=0x7f1b09019000, parser_state=0x7f1b4a8bb560) at /sda/mysql-server_dbg/sql/sql_parse.cc:5508
#19 0x00000000014e0d17 in dispatch_command (thd=0x7f1b09019000, com_data=0x7f1b4a8bbcb0, command=COM_QUERY) at /sda/mysql-server_dbg/sql/sql_parse.cc:1425
#20 0x00000000014dfbe1 in do_command (thd=0x7f1b09019000) at /sda/mysql-server_dbg/sql/sql_parse.cc:993
#21 0x000000000160adc7 in handle_connection (arg=0x7f1b343ff860) at /sda/mysql-server_dbg/sql/conn_handler/connection_handler_per_thread.cc:301
#22 0x000000000188e1b8 in pfs_spawn_thread (arg=0x7f1b31fec020) at /sda/mysql-server_dbg/storage/perfschema/pfs.cc:2192
#23 0x00007f1b4a2bedc5 in start_thread (arg=0x7f1b4a8bc700) at pthread_create.c:308
#24 0x00007f1b4850fced in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

How to repeat:
Testcase

create database test;
use test;
SET @@GLOBAL.innodb_compress_debug=3;
create table t (i int) engine=innodb;
insert into t values (1);

Hello Ramesh,

Thank you for the report and test case.
I'm not seeing this issue on 5.7.14. Is there anything else required to trigger this issue then my attempt? 

-- 5.7.14/5.7.15 debug builds with/without --no-defaults/sql_mode='' and/or ONLY_FULL_GROUP_BY, and/or punch hole support(src debug build)

rm -rf 82386
bin/mysqld --initialize-insecure --basedir=/export/umesh/server/binaries/GABuilds/mysql-advanced-5.7.14 --datadir=/export/umesh/server/binaries/GABuilds/mysql-advanced-5.7.14/82386 -v
bin/mysqld-debug --basedir=/export/umesh/server/binaries/GABuilds/mysql-advanced-5.7.14 --datadir=/export/umesh/server/binaries/GABuilds/mysql-advanced-5.7.14/82386 --core-file --socket=/tmp/mysql_ushastry.sock --port=3306 --log-error=/export/umesh/server/binaries/GABuilds/mysql-advanced-5.7.14/82386/log.err 2>&1 &

[umshastr@hod03]/export/umesh/server/binaries/GABuilds/mysql-advanced-5.7.14: bin/mysql -uroot -S /tmp/mysql_ushastry.sock
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 3
Server version: 5.7.14-enterprise-commercial-advanced-debug MySQL Enterprise Server - Advanced Edition Debug (Commercial)

Copyright (c) 2000, 2016, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql> drop database if exists test;
Query OK, 1 row affected (0.00 sec)

mysql> create database test;
Query OK, 1 row affected (0.00 sec)

mysql> use test;
Database changed
mysql> SET @@GLOBAL.innodb_compress_debug=3;
Query OK, 0 rows affected (0.00 sec)

mysql> create table t (i int) engine=innodb;
Query OK, 0 rows affected (0.00 sec)

mysql> insert into t values (1);
Query OK, 1 row affected (0.00 sec)

If you can provide more information, feel free to add it to this bug and change the status back to 'Open'.

Thanks,
Umesh

The reported problem was fixed in 5.7.13 along with

Bug#80182 Unsupported extension error for new features while 'create table like'

Hi Umesh,

Could not reproduce the issue with 5.7.14.

Thanks
Ramesh

Thank you Ramesh for confirming.
As per Erlend's note this is fixed.

Thanks,
Umesh