mariadb

Commit Graph

Author	SHA1	Message	Date
Daniel Black	3944655357	MDEV-37019 MSAN_STAT_WORKAROUND macro remove MSAN has been updated since 2022 when this macro was added and as such the working around MSAN's deficient understanding of the fstat/stat syscall behaviour at the time is no longer required. As an effective no-op a straight removal is sufficient.	5 months ago
Thirunarayanan Balathandayuthapani	4be442ec35	MDEV-36962 innodb.log_file_overwrite fails with ASAN Problem: ======= - InnoDB unpoisons the freed page memory to make sure that no other thread uses this freed page. In buf_pool_t::close(), InnoDB unmap() the buffer pool memory during shutdown or it encountered during startup. Later at some point, server re-uses the same virtual address using mmap() and writes into memory region. This leads to use_after_poison error. This issue doesn't happen in latest clang and gcc version. Older version of clang and gcc can still fail with this error. ASAN should unpoison the memory while reusing the same virtual address. This issue was already raised in https://github.com/google/sanitizers/issues/1705 Fix: === In order to avoid this failure, let's unpoison the buffer pool memory explictly during buf_pool_t::close() for lesser than gcc-14 and clang-18 version.	5 months ago
Kazuhiko Shiozaki	39ef6c0dc8	MDEV-34425 mroonga files are not copied by mariabackup Backing up with mariabackup a datadir containing ENGINE=Mroonga tables leaves behind the corresponding .mrn files. Those tables are therefore broken once such backup is restored. minor style/mtr changes by Daniel Black	6 months ago
Svante Signell	72d2b7697d	MDEV-12305 FTBFS on hurd-i386 due to PATH_MAX Hurd doesn't create PATH_MAX due its dogmatic standard approach. ref: https://www.gnu.org/software/hurd/hurd/porting/guidelines.html#PATH_MAX_tt_MAX_PATH_tt_MAXPATHL Origin: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069094	2 years ago
Daniel Black	22afd13e7a	Debian/Hurd doesn't support auth_socket Hurd doesn't have the mechanism to identify the user connecting to a socket via a system call as MDEV-8535 highlighted. As such it can't be supported so we disable it in Debian's mysql_release profile. Hurd string from uname -m, "SYSTEM processor: i686-AT386" in mariadb output. And wiki reference https://en.wikipedia.org/wiki/Uname Origin: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006531	10 months ago
Svante Signell	b490240263	Bug#1069094: mariadb: FTBFS on hurd-i386 Add Hurd to define __USE_FILE_OFFSET64 et al. Origin: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069094 Forwarded: no	2 years ago
Aleksey Midenkov	629b8d782c	MDEV-36662 CHECK constraint does not repeat in case of error CHECK constraint uses caching items and the value is cached even in case of error. At the second execution the cached value is taken and the error is not thrown. The fix does not cache value in case error was thrown during value retrieval.	5 months ago
Brad Smith	f66cd044d5	Enable use of elf_aux_info() to detect CPU features on aarch64 and powerpc64	5 months ago
Rex Johnston	729b27d390	MDEV-29300 Assertion `ref && (ref)->fixed()' failed in Item_field::fix_outer_field on SELECT This issue arises when we have an outer reference resolved in another outer reference where that outer reference is resolved in a outer select that is a grouping select. Under these circumstances, the intermediate item is wrapped in an Item_outer_ref and fixing is deferred later until fix_inner_refs. As this item wrapper isn't fixed we fail this assertion. The fix here is to resolve the item at the lowest level to the item inside the wrapper, which is fixed. This item can then get it's own wrapper pointing to the ultimate resolution of this item. Approved by Sanja Byelkin (sanja@mariadb.com) 2025-06-13	5 months ago
Raghunandan Bhat	7ba32f3ac8	MDEV-24588, 36851 followup: Fix derived, hybrid func test for --view-protocol	5 months ago
Brad Smith	fadfd9ea28	MDEV-37001 Enable building RocksDB on non-Linux aarch64 OSes Now that RocksDB has been synced up to 6.29 which includes the changes mentioned in the CMake comment support for building on non-Linux aarch64 OSes can be enabled.	6 months ago
Brad Smith	6d684b64d5	Rocksdb: Add missing getauxval() test for Linux	6 months ago
Aleksey Midenkov	f1f9284181	MDEV-34046 Parameterized PS converts error to warning, causes replication problems DELETE HISTORY did not process parameterized PS properly as the history expression was checked on prepare stage when the parameters was not yet substituted. In that case check_units() succeeded as there is no invalid type: Item_param has type_handler_null which is inherited from string type and this is valid type for history expression. The warning was thrown when the expression was evaluated for comparison on delete execution (when the parameter was already substituted). The fix postpones check_units() until the first PS execution. We have to postpone where conditions processing until the first execution and update select_lex.where on every execution as it is reset to the state after prepare.	5 months ago
raghunandanbhat	bff9b1e472	MDEV-36851: COALESCE() returns nullable column while IFNULL() does not Nullability is decided in two stages- 1. Based on argument NULL-ness Problem: - COALESCE currently uses a generic logic- "Result of a function is nullable if any of the arguments is nullable", which is wrong. - IFNULL sets nullability using second argument alone, which incorrectly sets the result to NULL even when first argument is not null. Fix: - Result of COALESCE and IFNULL is set to NULL only if all arguments are NULL. 2. Based on type conversion safety of fallback value Problem: - The generic `Item_hybrid_func_fix_attributes` logic would mark the function's result as nullable if any argument involved a type conversion that could yield NULL. Fix: - For COALESCE and IFNULL, nullability is set to NOT NULL if the first non-null argument can be safely converted to function's target return type. - For other functions, if any argument's conversion to target type could result in NULL, the function is marked nullable. Tests included in `mysql-test/main/func_hybrid_type.test`	6 months ago
Lena Startseva	c427618462	MDEV-36977: Histogram code lacks coverage for non-latin characters Added new testcases for histogram: - 3-byte characters - characters outside Basic Multilingual Plane	5 months ago
Vladislav Vaintroub	dd2982dc33	MDEV-30831 Cannot compile AWS KMS Plugin Fix AWS SDK build, it has changed substantionally since the plugin was introduced. There is now a bunch of intermediate C libraries, aws-cpp-crt and others, and for static linking, the link dependency must be declared. Also support AWS C++ SDK in vcpkg package manager.	5 months ago
Vladislav Vaintroub	5729d89cd5	MDEV-36938 Fix MSI install failure when ADDLOCAL omits required runtime Since 10.11.12 (commit `8363d05f4d`), executables are built with the dynamic C runtime (/MD), introducing a dependency on vcruntime140.dll. VC++ runtime is typically installed via the VCCRT feature, which is included by default as part of the hidden/default ALWAYSINSTALL feature set. However, when users specify the ADDLOCAL property, it overrides the default selection and may omit critical features like VCCRT. This leads to installation failures. Fix: Add a custom action that ensures mandatory features (e.g., VCCRT) are appended to the ADDLOCAL property at install time. This guarantees essential runtime components are always installed, even when a custom feature set is selected.	6 months ago
Sergei Petrunia	5a6732983d	MDEV-36461, followup: fix opt_trace.test for --view-protocol	5 months ago
Sergei Petrunia	cce76e7225	MDEV-36765: followup 4: Fixups to previous fixes - Add a testcase showing JSON_HB histograms handle multi-byte characters correctly. - Make Item_func_json_unquote::val_str() handle situation where it is reading non-UTF8 "JSON" and transcoding it into UTF-8. (the JSON spec only allows UTF8 but MariaDB's implementation supports non-UTF8 as well) - Make Item_func_json_search::compare_json_value_wild() handle json_unescape()'s return values in the same way its done in other places. - Coding style fixes.	5 months ago
Daniel Black	12c10712a7	MDEV-36765: followup 3: json_unquote/compare_json_str_basic handle errors from json_unescape Using report_json_error was incorrect as errors in the je have already been handled earlier in the json function. The errors related to json_unescape are handled with consistently with other functions.	6 months ago
Daniel Black	2b24ed87f0	MDEV-36765: followup 2: st_append_json: handle json_unescape error Now pushes the OUTOFMEMORY error and ER_JSON_BAD_CHAR as a warning if these resulted in those errors. callers only expected a bool so the prototype was changed. Json_engine_scan::check_and_get_value_scalar failed to handle the error condition so set the *error if an error occured and return the correct value.	6 months ago
Daniel Black	0dd758e5f9	MDEV-36765, followup 1: acl: handle json_unescape errors without crashing json_unescape can return negative numbers, and with so we should free the buffer allocated. Also handle the NULL value in unsafe_str by not de-referencing NULL.	6 months ago
Daniel Black	39bb34b9c5	MDEV-36765: JSON Histogram cannot handle >1 byte characters When json_escape changed[1] to return a -1 in the case of a character that didn't match the character set, json_unescape_to_string assumed the -1 meant out of memory and just looped with more memory. Problem 1 - json_escape needs to return a different code so that the different between charset incompatibility and out of memory needs to occur. This enables json_escape_to_string to handle the it correctly (ignore and fail seems the best option). Problem 2 - JSON histograms need to support character with where the column json min/maximum value aren't a character set represented by a single byte. Problem 2 was previously hidden as ? was a result of the conversion. As JSON histograms can relate to columns when have an explict character set, use that and fall back to bin which was the previous default for non-string columns. Replaces -1/-2 constants and handling with JSON_ERROR_ILLEGAL_SYMBOL / JSON_ERROR_OUT_OF_SPACE defines. [1] regression from: `f699010c0f`	6 months ago
Yuchen Pei	11d1ac7285	MDEV-35856 Remove error code introduced to 10.11 in MDEV-36032 Two new error codes ER_SEQUENCE_TABLE_HAS_TOO_FEW_ROWS and ER_SEQUENCE_TABLE_HAS_TOO_MANY_ROWS were introduced in MDEV-36032 in both 10.11 and, as part of MDEV-22491, 12.0. Here we remove them from 10.11, but they should remain in 12.0.	6 months ago
Oleksandr Byelkin	28d6530571	Merge branch '10.6' into 10.11	6 months ago
Raghunandan Bhat	e7aaf29e00	MDEV-24588: Fix crash with unnamed column in derived table MariaDB server crashes when a query includes a derived table containing unnamed column (eg: `SELECT '' from t`). When `Item` object representing such unnamed column was checked for valid, non-empty name in `TABLE_LIST::create_field_translation`, the server crahsed(assertion `item->name.str && item->name.str[0]` failed). This fix removes the redundant assertion. The assert was a strict debug guard that's no longer needed because the code safely handles empty strings without it. Selecting `''` from a derived table caused `item->name.str` to be an empty string. While the pointer itself wasn't `NULL` (`item->name.str` is `true`), its first character (`item->name.str[0]`) was null terminator, which evaluates to `false` and eventually made the assert fail. The code immediately after the assert can safely handle empty strings and the assert was guarding against something which the code can already handle. Includes `mysql-test/main/derived.test` to verify the fix.	6 months ago
Aleksey Midenkov	5ff01ad7bb	MDEV-33370 Assertion `!is_set() \|\| (m_status == DA_OK_BULK && is_bulk_op())' failed after ALTER TABLE of versioned table Missed error code resulted in my_ok() at higher frame which failed on assertion for m_status in state of error.	6 months ago
Brad Smith	6409e43177	Replace deprecated CMAKE_COMPILER_IS_GNU(CC\|CXX) with CMAKE_(C\|CXX)_COMPILER_ID As of CMake 3.24 CMAKE_COMPILER_IS_GNU(CC\|CXX) are deprecated and should be replaced with CMAKE_(C\|CXX)_COMPILER_ID which were introduced with CMake 2.6.	6 months ago
Daniel Black	5cd982c51b	MDEV-34863 RAM Usage Changed Significantly Between 10.11 Releases (postfix) Correct error message to use the correct system variable name - innodb_buffer_pool_size_auto_min	6 months ago
Monty	643319a7fb	MDEV-36465 MDEV-33813 Regression, Queries in 'Waiting for someone to free space' state will not automatically retry IO and hang forever MDEV-33813 caused a regressing in that when a disk got full when writing to a MyISAM or Aria table the MariaDB connection would, instead of doing a retry after 60 seconds, hang until the query was killed. Fixed by changing mysql_coind_wait() top mysql_cond_timedwait() Author: Thomas Stangner	6 months ago
Monty	0a91bbdc41	Get debug version to compile with gcc 7.5.0	6 months ago
Monty	ce4f83e6b9	MDEV-29157 SELECT using ror_merged scan fails with s3 tables handler::clone() call did not work with read only tables like S3. It gave a wrong error message (out of memory instead of a permission error) and aborted the query. The issue was that the clone call had a wrong parameter to ha_open(). This now fixed. I also changed the clone call to provide the correct error message if things fails. This patch fixes an 'out of memory' error when using the S3 engine for queries that could use multiple indexes together to find the matching rows, like the following: SELECT * FROM t1 WHERE key1 = 99 OR key2 = 2	6 months ago
Monty	5f83b219bb	Fixed compiler warning from clang in connect/tabxcl.cpp	6 months ago
Monty	6878c14000	Updated storage/maria/ma_test_big.sh to use aria_ instead of maria_ I also improved the script to use 'tmp' for storing test files instead of current directory	6 months ago
Monty	22024da64e	MDEV-36143 Row event replication with Aria does not honour BLOCK_COMMIT This commit fixes a bug where Aria tables are used in (master->slave1->slave2) and a backup is taken on slave2. In this case it is possible that the replication position in the backup, stored in mysql.gtid_slave_pos, will be wrong. This will lead to replication errors if one is trying to use the backup as a new slave. Analyze: Replicated row events are committed with trans_commit_stmt() and thd->transaction->all.ha_list != 0. This means that backup_commit_lock is not taken for Aria tables, which means the rows are committed and binary logged on the slave under BLOCK_COMMIT which should not happen. This issue does not occur on the master as thd->transaction->all.ha_list is == 0 under AUTO_COMMIT, which sets 'is_real_trans' and 'rw_trans' which in turn causes backup_commit_lock to be taken. Fixed by checking in ha_check_and_coalesce_trx_read_only() if all handlers supports rollback and if not, then wait for BLOCK_COMMIT also for statement commit.	6 months ago
Daniel Black	f533333f82	MDEV-34388: Stack overflow on Alpine Linux (postfix) - sanitizers Remove stack limits for sanitizers. Other tests cover them.	6 months ago
Aleksey Midenkov	fe6a5c2200	MDEV-29155 CREATE OR REPLACE with self-referencing CHECK hangs forever, cannot be killed mysql_rm_table_no_locks() does TDC_RT_REMOVE_ALL which waits while share is closed. The table normally is open only as OPEN_STUB, this is what parser does for CREATE TABLE. But for SELECT the table is opened not as a stub. If it is the same table name we anyway have two TABLE_LIST objects: stub and not stub. So for "not stub" TDC_RT_REMOVE_ALL sees open count and decides to wait until it is closed. And it hangs because that was opened in the same thread. The fix disables subqueries in CHECK expression at parser level. Thanks to Sergei Golubchik <serg@mariadb.org> for the patch.	6 months ago
Aleksey Midenkov	0b2434d2e9	MDEV-25158 Segfault on INTERSECT ALL with UNION in Oracle mode Oracle mode has different set operator precedence and handling (not by standard). In Oracle mode the below test case is handled as-is, in plain order from left to right. In MariaDB default mode follows SQL standard and makes INTERSECT prioritized, so UNION is taken from derived table which is INTERSECT result (here and below the same applies for EXCEPT). Non-distinct set operator (UNION ALL/INTERSECT ALL) works via unique key release but it can be done only once. We cannot add index to non-empty heap table (see heap_enable_indexes()). So every UNION ALL before rightmost UNION DISTINCT works as UNION DISTINCT. That is common syntax, MySQL, MSSQL and Oracle work that way. There is union_distinct property which indicates the rightmost distinct UNION (at least, so the algorithm works simple: it releases the unique key after union_distinct in the loop (st_select_lex_unit::exec()). INTERSECT ALL code (implemented by MDEV-18844 in `a896beb`) does not know about Oracle mode and treats union_distinct as the last operation, that's why it releases unique key on union_distinct operation. INTERSECT ALL requires unique key for it to work, so before any INTERSECT ALL unique key must not be released (see select_unit_ext::send_data()). The patch tweaks INTERSECT ALL code for Oracle mode. In disable_index_if_needed() it does not allow unique key release before the last operation and it allows unfold on the last operation. Test case with UNION DISTINCT following INTERSECT ALL at least does not include invalid data, but in fact the whole INTERSECT ALL code could be refactored for better semantical triggers. The patch fixes typo in st_select_lex_unit::prepare() where have_except_all_or_intersect_all masked eponymous data member which wrongly triggered unique key release in st_select_lex_unit::prepare(). The patch fixes unknown error in case ha_disable_indexes() fails. Note: optimize_bag_operation() does some operator substitutions, but it does not run under PS. So if there is difference in test with --ps that means non-optimized (have_except_all_or_intersect_all == true) code path is not good. Note 2: VIEW is stored and executed in normal mode (see Sql_mode_save_for_frm_handling) hence when SELECT order is different in Oracle mode (defined by parsed_select_expr_cont()) it must be covered by --disable_view_protocol.	6 months ago
Daniel Black	e021a61b6f	MDEV-36729: ha_example::show_func_example is incorrectly defined In the main.plugin this function is called assuming the function prototype int ()(THD , st_mysql_show_var , void , system_status_var *, enum_var_type)' as changed in `b4ff64568c`. We update the ha_example::show_func_example to match the prototype on which it is called.	7 months ago
Marko Mäkelä	4d37b1c4b9	MDEV-36886 log_t::get_lsn_approx() isn't lower bound If the execution of the two reads in log_t::get_lsn_approx() is interleaved with concurrent writes of those fields in log_t::write_buf() or log_t::persist(), the returned approximation will be an upper bound. If log_t::append_prepare_wait() is pending, the approximation could be a lower bound. We must adjust each caller of log_t::get_lsn_approx() for the possibility that the return value is larger than MAX(oldest_modification) in buf_pool.flush_list. af_needed_for_redo(): Add a comment that explains why the glitch is not a problem. page_cleaner_flush_pages_recommendation(): Revise the logic for the unlikely case cur_lsn < oldest_lsn. The original logic would have invoked af_get_pct_for_lsn() with a very large age value, which would likely cause an overflow of the local variable lsn_age_factor, and make pct_for_lsn a "random number". Based on that value, total_ratio would be normalized to something between 0.0 and 1.0. Nothing extremely bad should have happened in this case; the innodb_io_capacity_max should not be exceeded.	6 months ago
Marko Mäkelä	7b4b759f13	MDEV-36868: Inconsistency when shrinking innodb_buffer_pool_size buf_pool_t::resize(): After successfully shrinking the buffer pool, announce the success. The size had already been updated in shrunk(). After failing to shrink the buffer pool, re-enable the adaptive hash index if it had been enabled. Reviewed by: Debarun Banerjee	6 months ago
Daniel Black	88d35c5c51	MDEV-34388: Stack overflow on Alpine Linux (postfix) mroonga+asan The following mroonga functions had approaching 64k stack frames, so exclude these: * chunk_merge - ~60k * buffer_merge - ~78k * grn_ii_update_one - ~60k	6 months ago
Daniel Black	676aea8cad	MDEV-36848: identify tests with various MSAN suitability With MSAN the following test behavious where observed: * funcs_1.myisam_views-big - normal big test for non-debug * innodb_gis.rtree_purge - normal big test with MSAN * main.alter_table_lock - very quick - unclear why disabled * main.cte_recursive - slow on Debug only * main.join_cache_notasan - special MSAN handing for returning OOM added * main.sum_distinct-big - 90 seconds on non-debug - still big however * maria.max_length - normal big test with MSAN * perfschema.statement_digest_long_query - overflows stack on debug Timingsi (on old memory constrained hardware): non-debug: funcs_1.myisam_views-big w2 [ pass ] 78564 innodb_gis.rtree_purge '16k' w2 [ pass ] 5784 innodb_gis.rtree_purge '32k' w2 [ pass ] 5242 innodb_gis.rtree_purge '4k' w1 [ pass ] 8303 innodb_gis.rtree_purge '64k' w1 [ pass ] 6348 innodb_gis.rtree_purge '8k' w2 [ pass ] 5870 main.alter_table_lock w1 [ pass ] 41 main.cte_recursive w1 [ pass ] 15485 main.join_cache_notasan w1 [ pass ] 39 main.sum_distinct-big w2 [ pass ] 96256 maria.max_length w1 [ pass ] 92990 perfschema.statement_digest_long_query w2 [ pass ] 8 debug: funcs_1.myisam_views-big w1 [ skipped ] Can't be run WITH_MSAN and CMAKE_BUILD_TYPE=Debug innodb_gis.rtree_purge '16k' w2 [ pass ] 109788 innodb_gis.rtree_purge '32k' w2 [ pass ] 62361 innodb_gis.rtree_purge '4k' w1 [ pass ] 89423 innodb_gis.rtree_purge '64k' w1 [ pass ] 72082 innodb_gis.rtree_purge '8k' w1 [ pass ] 98452 main.alter_table_lock w2 [ pass ] 38 main.cte_recursive w2 [ pass ] 180047 main.join_cache_notasan w1 [ pass ] 166 main.sum_distinct-big w1 [ skipped ] Can't be run WITH_MSAN and CMAKE_BUILD_TYPE=Debug maria.max_length w1 [ skipped ] Can't be run WITH_MSAN and CMAKE_BUILD_TYPE=Debug perfschema.statement_digest_long_query w1 [ skipped ] Can't be run WITH_MSAN and CMAKE_BUILD_TYPE=Debug	6 months ago
Daniel Black	5dbfb52d04	MDEV-36894 JSNX::SetArrayOptions and BJNX::SetArrayOptions unused nm arg Calling SetArrayOptions with Nodes[i - 1].Key as its nm argument exposed a MemorySanitizer error when i=0 for the tests: * connect.bson_udf * connect.json_udf * connect.json_udf_bin Its assumed that a basic optimization would have eliminated these invalid expressions. As the nm argument was unused, it has been removed.	6 months ago
Daniel Black	495153feac	MDEV-36893 THD::reset_sub_statement_state swaps with uninitialized structure THD::reset_sub_statement_state and THD::restore_sub_staement_state swap auto_inc_intervals_forced(Discrete_intervals_list) of a THD class with a local variable temporary to execute other things before restoring at the end of Table_triggers_list::process_triggers under a rpl_master_erroneous_autoinc(true) condition as exposed by the rpl.rpl_trigger test. The uninitialized data isn't used and the only required action is to copy the data in one direction. As the intent is for the auto_inc_intervals_forced value to be overwritten or unused, MEM_UNDEFINED is used on it to ensure the previous state is considered invalid. The other uses of reset_sub_statement_state in Item_sp::execute_impl also follow the same pattern of taking a copy to restore within the same function.	6 months ago
Daniel Black	8d2665e56b	MDEV-34388 default stack size under MSAN needs increasing Without this increase the mtr test case pre/post conditions will fail as the stack usage has increased under MSAN with clang-20.1. ASAN takes a 11M stack, however there was no obvious gain in MSAN test success after 2M. The resulting behaviour observed on smaller stack size was a SEGV normally. Hide the default stack size from the sysvar tests that expose thread-stack as a variable with its default value.	8 months ago
Daniel Black	2811559337	version string - memory sanitizer isn't the same as valgrind Despite being included in the HAVE_valgrind define. As such it's best differenciated from valgrind in the server identifier as they have for the purposes a distinct and different set of behaviours. MSAN has its own set of test inclusions that that are different from valgrind and such including "valgrind" in a server string that gets tested for valgrind will incorrectly exclude some tests that are suitable for MSAN but not valgrind. There's a have_sanitizer system variable for exposing the sanitizer being used so there's no need for version verboseness. Correct have_sanitizer system variable description to include MSAN has been possible for a while.	6 months ago
Daniel Black	8490901307	MDEV-34388: Stack overflow on Alpine Linux (postfix - ASAN/MSAN+Debug) In original fix, commit `82d7419e06`, a 16k stack frame limit was imposed. Under the stack usage is doubled due to MSAN. Debug builds without optimization can use more as well. ASAN Debug builds also exceeded the 16k stack frame limit. To keep some safety limit, a 64k limit is imposed to the compiler under MSAN or ASAN with CMAKE_BUILD_TYPE=Debug.	6 months ago
Marko Mäkelä	5012402330	MDEV-34388 Alpine Stack Overflow - reduce Grant_tables::open_and_lock The stacksize was still too large. Back port from the 10.11 merge commit `1c7209e828`	6 months ago
Daniel Black	df414933f1	MDEV-36316/MDEV-36327/MDEV-36328 Debug msan Clang ~16+ on MSAN became quite strict with uninitalized data being passed and returned from functions. Non-debug builds have a basic optimization that hides these from those builds Two innodb cases violate the assumptions, however once inlined with a basic optimization those that existed for uninitialized values are removed. (MDEV-36316) rec_set_bit_field_2 calling mach_read_from_2 hits a read of bits it wasn't actually changing. (MDEV-36327) The function dict_process_sys_columns_rec left nth_v_col uninitialized unless it was a virtual column. This was ok as the function i_s_sys_columns_fill_table also didn't read this value unless it was a virtual column.	6 months ago

1 2 3 4 5 ...

201573 Commits (39446553577041f7f479052f500183cf86a8b8e7) All Branches Search

201573 Commits (39446553577041f7f479052f500183cf86a8b8e7)

All Branches