mirror of
https://github.com/MariaDB/server.git
synced 2025-07-30 16:24:05 +03:00
MDEV-17869 AddressSanitizer: use-after-poison in Item_change_list::rollback_item_tree_changes
it's incorrect to use change_item_tree() to replace arguments of top-level AND/OR, because they (arguments) are stored in a List, so a pointer to an argument is in the list_node, and individual list_node's of top-level AND/OR can be deleted in Item_cond::build_equal_items(). In that case rollback_item_tree_changes() will modify the deleted object. Luckily, it's not needed to use change_item_tree() for top-level AND/OR, because the whole top-level item is copied and preserved in prep_where and prep_on, and restored from there. So, just don't. Additionally to the test case in the commit it fixes * ASAN failure of main.opt_tvc --ps * ASAN failure of main.having_cond_pushdown --ps
This commit is contained in:
@ -52,3 +52,20 @@ execute p1 using 17864960750176564435;
|
||||
--echo #
|
||||
--echo # End of 10.3 tests
|
||||
--echo #
|
||||
|
||||
--echo #
|
||||
--echo # MDEV-17869 AddressSanitizer: use-after-poison in Item_change_list::rollback_item_tree_changes
|
||||
--echo #
|
||||
create table t1 (pk int, v1 varchar(1));
|
||||
insert t1 values (1,'v'),(2,'v'),(3,'c');
|
||||
create table t2 (pk int, v1 varchar(1));
|
||||
insert t2 values (1,'x');
|
||||
create table t3 (pk int, i1 int, v1 varchar(1));
|
||||
insert t3 values (10,8,9);
|
||||
execute immediate 'select straight_join 1 from (t1 join t2 on (t1.v1 = t2.v1))
|
||||
where (3, 6) in (select tc.pk, t3.i1 from (t3 join t1 as tc on (tc.v1 = t3.v1)) having tc.pk > 1 );';
|
||||
drop table t1, t2, t3;
|
||||
|
||||
--echo #
|
||||
--echo # End of 10.4 tests
|
||||
--echo #
|
||||
|
Reference in New Issue
Block a user