Home - Waterfall Grid T-Grid Console Builders Recent Builds Buildslaves Changesources - JSON API - About

Console View


Categories: connectors experimental galera main
Legend:   Passed Failed Warnings Failed Again Running Exception Offline No data

connectors experimental galera main
f3f27f0badbc...
f3f27f0badbc659415658c1493524be7615ed7ac
Teemu Ollakka
fix galera_bf_abort_orphan_lock: use transaction_isolation

tx_isolation is deprecated and now emits a warning, which broke
the test's expected result. Use the non-deprecated
transaction_isolation instead.
ee276d1918e0...
ee276d1918e05e6f22c800bac0af6f5dbeedc8af
Marko Mäkelä
squash! e16b1b4e2739be7bc8e91643b0a71e1f04a1b02f

Ensure the minimum file size
eb7f31aa30d2...
eb7f31aa30d2479464116cf11c43ac6c7cdf9d5a
Marko Mäkelä
fixup! e16b1b4e2739be7bc8e91643b0a71e1f04a1b02f

Try harder to fix a hang of mariabackup.huge_lsn,SERVER,strict_full_crc32
e46da1ca8857...
e46da1ca8857dfa5f79e219ea1f7db817fd0b947
Oleksandr Byelkin
Merge fix
e3d62d4e78fd...
e3d62d4e78fd4941cef3f5053e6a50d0b32d740e
Sergei Golubchik
MDEV-40629 environment injection via wsrep bootstrap in the service file

* don't create mariadb-wsrep-new-cluster in the mariadbd-writable path,
  the server should not be able to poison the environment with OUTFILE.
  Create it in /run
* As in /run it must be deleted by root, let galera_new_cluster delete
  it, not the service
* wsrep-start-position cannot be created by root, so avoid a file
  for it at all

Assisted-By: Claude:claude-5-opus
e2e5c5e34285...
e2e5c5e34285ae59481bf5d65181ab4a3d812dfd
Marko Mäkelä
fixup! bfed32bb60c003fbe974f60f925c8da20ef35adf
d366ed51c490...
d366ed51c490f688bc8e2ab0e9e2bd85f92c6edf
Brandon Nesterenko
MDEV-40643 (Regression): Corrupt Heartbeat Log Event can Crash Slave
d3601f8aba52...
d3601f8aba5235d033dbf112435119aadfcc4450
Brandon Nesterenko
MDEV-40643: Corrupt Heartbeat Log Event can Crash Slave

A slave can crash when its master sends an event shorter than the
event's own header. A truncated heartbeat makes debug builds fail an
assertion in Binary_string::realloc_raw(). On 64-bit release builds it
stops the slave IO thread with an error message that omits the log
file name. If the master also declares an oversized common header in
its format description event, the slave allocates and fills nearly 4GB
instead. On 32-bit release builds it writes that error message past
the end of a stack buffer. An event under four bytes crashes every
build, because the slave checksums roughly 16 EiB and reads far past
the end of the packet.

Neither queue_event() nor the Heartbeat_log_event constructor bounded
the length the master sent. queue_event() handed that length to
event_checksum_test(), which subtracted the checksum length from it,
and the result wrapped on an event under four bytes. The constructor
computed the log file name length as event_len minus the header
lengths, and on a truncated heartbeat that subtraction wrapped to a
value near 4GB. queue_event() rejected the heartbeat as invalid, so
its error path appended the log file name to the error message using
the wrapped length.

Add the missing bound in both places. queue_event() now rejects an event
shorter than the common header before anything reads that header, and
the slave IO thread stops with an error. The Heartbeat_log_event
constructor now compares event_len against the combined header lengths
before the subtraction. A heartbeat that clears the first check but
still stops inside its headers keeps ident_len at 0 and log_ident at
NULL, so the error path appends nothing. That constructor check also
precedes the read of the extended log position, which previously ran on
a short event before any validation. A short event from the master now
stops the slave IO thread with an error instead of crashing the server.

Reviewed-by: TODO
Signed-off-by: Brandon Nesterenko <[email protected]>
cd7b01409fec...
cd7b01409fecebd1453d8eb412c7b8ec62ffaaa1
Dave Gosselin
Clarify NULL handling comment in next_min()
cc64459f1c09...
cc64459f1c09274ceb19250d6c8867fc1f3df631
Oleksandr Byelkin
Merge branch 'bb-10.11-release' into bb-11.4-release
cb5a92348ebb...
cb5a92348ebb37ab690338c0391b717ae66c6fb8
Marko Mäkelä
fixup! a8fcc6617fe752014462a8b57e79c4102144dd14
c920fcf4789c...
c920fcf4789c1e918dbdd45e341d941f02743312
Oleksandr Byelkin
Merge branch '11.4' into bb-11.4-release
ba314311544b...
ba314311544b163f2581c98b4361cc4f21d26d0c
Teemu Ollakka
crash in wsrep_provider_options_init() with wsrep provider plugin

wsrep_provider_plugin_init() marked wsrep_provider_options read only
by mutating the sys_var's flags directly, instead of going through the
sys_var layer. Since MDEV-40341 move_allocated_sysvars_to_root() moves
the value of every read only global string sysvar into the read only
memroot and clears the ALLOCATED flag. wsrep_provider_options_init()
then called my_free() on memroot memory, which aborted on the garbage
allocation header.

Remove the flag mutation instead of working around its effects.
wsrep_provider_options stays a normal read-write variable and is kept
in sync with the provider whenever a plugin sysvar changes.

SET on wsrep_provider_options is still rejected while the
wsrep-provider plugin is loaded, via the existing
wsrep_provider_options_check() function. Its error message now states
the real reason instead of "is a read only variable", which was
misleading: the variable is not statically read only, and
information_schema correctly reports READ_ONLY=NO for it.
b82153efed4c...
b82153efed4c74085e70e52b30d952dd7881d8fa
Dave Gosselin
Clarify NULL handling comment in next_min()
947765870d6b...
947765870d6bb3795b805d2c387aea1cb44dc64f
bsrikanth-mariadb
MDEV-40383:innodb_gis.point_basic fails on replay

There are 2 problems: -
1. The REPLACE statement that is recorded doesn't store the
  value of geometry type field correctly.
2. The table definition that got recorded has fields with non-null constraint,
  and no default value is specified.
  Also, the "REPLACE INTO" statement that gets stored in the context,
  doesn't have any value specified for these non-null fields.

Solution is to: -
1. When using REPLACE INTO statement, store all the non-numeric values in HEX,
  whenever conversion from field's charset to output's charset is lossy.
2. Instead of storing only the column values that were projected in the
  query, store all the non-virtual column values into the recorded
  REPLACE INTO statement.

Implementation details: -
1. Introduce a new method is_charset_conversion_lossless() in filesort.cc,
  to check if the output charset to which field's data is being written to,
  results in a lossless conversion. If so, non-numeric values being witten
  using REPLACE INTO statement are stored in string representation,
  else they are converted to HEX.
2. Modify join_read_const(), and join_read_system() methods in sql_select.cc,
  and opt_sum_query() method in opt_sum.cc the following way: -
    a. Extend the read_set to make sure, we read all the non-virtual column
        using Optimizer_context_recorder::prepare_captured_row_read().
        This method also saves the original read_set.
    b. Read the row.
    c. Dump the row into the context when no error is noticed while
        reading. Irrespective of the error, restore back the read_set state to
        the original using Optimizer_context_recorder::finish_captured_row_read()
940b8daa5132...
940b8daa5132a8e8ba661f499659eb9ddf4722ed
Sergei Golubchik
cleanup: encryption.filekeys_encfile_badfile

combine all tests for wrong FILE: values into one test
add a test for a wrong key.
907385c2f13c...
907385c2f13c14150abcc4c655e9363493a87ac8
Vladislav Vaintroub
MDEV-33387 - multifactor authentication

Support "AND" between authentication plugins in CREATE/ALTER USER, so
that a user must pass every factor to log in (multi-factor auth), in
addition to the existing "OR" (alternative plugins). Mixing AND and OR
in one user definition is rejected.

  CREATE USER u IDENTIFIED VIA mysql_native_password AS PASSWORD('...')
                      AND some_other_plugin USING '...';

Grammar and storage
  - USER_AUTH gets a logical_operator (NONE/OR/AND) telling how each factor
    combines with the next; the parser tags the factor list and rejects a
    mix of AND/OR.
  - The operator is persisted in mysql.global_priv: the factor array is
    stored under "auth_and" (mirroring the existing "auth_or"). ALTER USER
    that collapses a multi-factor account back to a single plugin removes
    the stale "auth_and"/"auth_or" key.
  - SHOW CREATE USER prints " AND " between factors.
  - Two password-based (hashing) plugins in one AND chain are rejected;
    at most one factor may carry a password hash.

Authentication protocol
  - New client capability CLIENT_MULTI_FACTOR_AUTHENTICATION and an
    AuthNextFactor (0x02) command that tells the client to proceed to the
    next factor after the current one succeeded. send_plugin_request_packet
    becomes send_change_plugin_packet, handling both the auth-switch (0xFE)
    and next-factor (0x02) commands. Clients that do not announce the
    capability fall back to an auth switch.
  - acl_authenticate() runs the factors sequentially for AND (every factor
    must return CR_OK), while OR keeps its "first success wins" behavior.
  - The in-server client (sql-common/client.c, used by mariadb-backup,
    replication, etc.) also handles AuthNextFactor: it advertises the new
    capability, recognises the 0x02 packet in run_plugin_auth(), and uses
    the same is_auth_switch_command() helper (with AUTH_SWITCH_PLUGIN_PACKET
    and AUTH_NEXT_FACTOR_PACKET symbolic constants) as libmariadb does.

TLS server-identity via password hash
  - When the connection uses a self-signed certificate and no CA is
    configured, the server sends a fingerprint challenge in the OK packet,
    computed from the certificate fingerprint and the password hash. For a
    multi-factor account the salt of the first password-hashing factor is
    used. The client recomputes it and, on a match, trusts the certificate
    even with --ssl-verify-server-cert, so password-based verification of
    the server does not raise a certificate error.

Tests
  - New plugins suite tests: mfa (portable machinery: AuthNextFactor round
    trip, non-hashing factor, auth_and persistence and ALTER round-trip,
    distinct per-factor secrets, negative cases, TLS fingerprint),
    mfa_unix (unix_socket + password), mfa_win (named_pipe/gssapi +
    password), mfa_unix_pam (password + PAM PIN).
  - auth_gssapi multiauth trimmed to the OR cases it still owns.

Client side changes are in the bundled libmariadb (submodule bump).

Assisted-by: Claude:claude-haiku-4.5-20251001

MDEV-33387 fix --plugin-dir for mariabackup tests
8a831e691e94...
8a831e691e94851dcfede41c921536d355a5ff41
PranavKTiwari
CIDR
8658d12a2f89...
8658d12a2f89633fdee802f5999db1d613e7da31
Oleksandr Byelkin
Merge branch '10.6' into 10.11
7bf109aa72ff...
7bf109aa72ffb270b142d61876d785a697eaac2e
Sergei Golubchik
don't put WITH_WSREP into my_config.h

it confuses plugins, when installed
74e5de7ea26d...
74e5de7ea26d44868b4f1a3248f4022fa15ec33b
bsrikanth-mariadb
MDEV-40383:innodb_gis.point_basic fails on replay

There are 2 problems: -
1. The REPLACE statement that is recorded doesn't store the
  value of geometry type field correctly.
2. The table definition that got recorded has fields with non-null constraint,
  and no default value is specified.
  Also, the "REPLACE INTO" statement that gets stored in the context,
  doesn't have any value specified for these non-null fields.

Solution is to: -
1. When using REPLACE INTO statement, store all the non-numeric values in HEX,
  whenever conversion from field's charset to output's charset is lossy.
2. Instead of storing only the column values that were projected in the
  query, store all the non-virtual column values into the recorded
  REPLACE INTO statement.

Implementation details: -
1. Introduce a new method is_charset_conversion_lossless() in filesort.cc,
  to check if the output charset to which field's data is being written to,
  results in a lossless conversion. If so, non-numeric values being witten
  using REPLACE INTO statement are stored in string representation,
  else they are converted to HEX.
2. Modify join_read_const(), and join_read_system() methods in sql_select.cc,
  and opt_sum_query() method in opt_sum.cc the following way: -
    a. Extend the read_set to make sure, we read all the non-virtual column
        using Optimizer_context_recorder::prepare_captured_row_read().
        This method also saves the original read_set.
    b. Read the row.
    c. Dump the row into the context when no error is noticed while
        reading. Irrespective of the error, restore back the read_set state to
        the original using Optimizer_context_recorder::finish_captured_row_read()
6fb7e416462f...
6fb7e416462ff02af3bbc81ccebc840482b382b1
drrtuy
fix: MDEV-40610 fix for SQL injection in DEFAULT expression.
6ed10c04f001...
6ed10c04f0013c901f897f422ceb699516bf5ee5
Marko Mäkelä
squash! e16b1b4e2739be7bc8e91643b0a71e1f04a1b02f

Aria_backup::is_db_file(): Filter out #sql file names.
69ce9cbcc2d8...
69ce9cbcc2d8443777895ea808aba62dd5a568a2
Sergei Golubchik
MDEV-40658 file_key_management crash on empty FILE: file
65d4e16e79f0...
65d4e16e79f094ae5b9fc884a9ac57dc1c6e4854
Dave Gosselin
MDEV-25964:  Unexpected bypass of lock

When an uncommitted transaction inserts rows into a table and
another statement locks rows in the same table (SELECT ... FOR UPDATE)
while computing a MIN or MAX, then:
  1. In a Debug build, the server aborts on an assertion
  2. In a Release build, the server returns wrong results
These errors occur because, while reading a group of rows for computing
a MAX, the transaction timeout error was swallowed.

Under the scenario described above and captured in the new test at this
commit, QUICK_GROUP_MIN_MAX_SELECT::next_max() emits a lock timeout error
during QUICK_GROUP_MIN_MAX_SELECT::get_next() but the error was suppressed
if we computed a MIN.

The InnoDB storage engine has an unwritten convention that after it has
returned a fatal error (which is any error except HA_ERR_END_OF_FILE
or HA_ERR_KEY_NOT_FOUND), then the SQL layer should not try to make
any further reads.  This is because InnoDB might have rolled back
the current transaction already.  So in the case of an error, return
immediately from QUICK_GROUP_MIN_MAX_SELECT::get_next().
5d56b948430e...
5d56b948430e870a0b12f16d9d2e7ce1bf1af974
Vladislav Vaintroub
MDEV-40656 Bypass REVOKE DENY ... FROM PUBLIC privilege check.

DENY ... TO PUBLIC denies everyone, including whoever tries to revoke
it, via the "deny wins" merge at every scope (global, db, table, column,
routine). Allow REVOKE DENY ... FROM PUBLIC when the revoker can UPDATE
mysql.global_priv (same as hand-editing).

Assisted-by: Claude:claude-5-sonnet
5c80e650e958...
5c80e650e9584ed43d8a4581f5d8f19128ab4f43
Oleksandr Byelkin
Merge branch '10.11' into bb-10.11-release
574ba66b2d6c...
574ba66b2d6c5d71db83d416677876e9b592858e
Sergei Golubchik
MDEV-40362 fix test

followup for f277eefa424
402622c0dc6d...
402622c0dc6d547117637e00138ac5fad8bbcaa0
Marko Mäkelä
fixup! 23ecceccc6201b2122ee946a05e5860f8a2fadb6

btr_search_drop_page_hash_index() is being invoked on a non-file page
(state < FREED). Everywhere else, the more readable
!is_read_fixed() or !is_io_fixed() assertions are safe to use.
3f9f33cf9cf5...
3f9f33cf9cf5c973a769d948c55d09e46492bf61
sjaakola
MDEV-36677 rsync sst fails with different innodb_log_group_home_dir and datadir

Backported the fix done by Pekka Lampio for mariaDB 11.4 in PR
https://github.com/mariadb-corporation/codership-mariadb-server/pull/543

The PR has a fix for wsrep_sst_rsync script and new mtr test:
galera_3nodes.galera_mdev_36677" to check that the rsync SST method of Galera
works correctly also when the joiner node store InnoDB log files in a dedicated
directory separate from the data dictionary

Note: merging this PR to 11.4 may not be fully functional as there are other
changes in the rsync SST script. Take a look at the original 11.4 PR when merging.
3c6a31852e9c...
3c6a31852e9ceb2059748218a973402b78227cf6
PranavKTiwari
Fixed macor
34854f5e43ea...
34854f5e43ea1ac7b8c17aa9a263831b92acae03
Fariha Shaikh
MDEV-39459 Fix bad sync pattern for chain replication MTR tests

In chain replication (1->2->3), syncing only server_3 after
save_master_gtid on server_1 does not guarantee server_2 has committed,
because server_2's binlog dump thread can send events to server_3 before
commit_ordered() completes on server_2.

Fix affected rpl tests by syncing server_2 before server_3, and update
result files accordingly.

All new code of the whole pull request, including one or several files
that are either new files or modified ones, are contributed under the
BSD-new license. I am contributing on behalf of my employer Amazon Web
Services, Inc.
23ecceccc620...
23ecceccc6201b2122ee946a05e5860f8a2fadb6
Marko Mäkelä
fixup! cb5a92348ebb37ab690338c0391b717ae66c6fb8
1caecf944f90...
1caecf944f90872f48745491094162bfb3a98890
Dave Gosselin
MDEV-25964:  Unexpected bypass of lock

When an uncommitted transaction inserts rows into a table and
another statement locks rows in the same table (SELECT ... FOR UPDATE)
while computing a MIN or MAX, then:
  1. In a Debug build, the server aborts on an assertion
  2. In a Release build, the server returns wrong results
These errors occur because, while reading a group of rows for computing
a MAX, the transaction timeout error was swallowed.

Under the scenario described above and captured in the new test at this
commit, QUICK_GROUP_MIN_MAX_SELECT::next_max() emits a lock timeout error
during QUICK_GROUP_MIN_MAX_SELECT::get_next() but the error was suppressed
if we computed a MIN.

The InnoDB storage engine has an unwritten convention that after it has
returned a fatal error (which is any error except HA_ERR_END_OF_FILE
or HA_ERR_KEY_NOT_FOUND), then the SQL layer should not try to make
any further reads.  This is because InnoDB might have rolled back
the current transaction already.  So in the case of an error, return
immediately from QUICK_GROUP_MIN_MAX_SELECT::get_next().
0ed5acbedc40...
0ed5acbedc40ad88a772809271e0ce387ab063f0
Vladislav Vaintroub
MDEV-40656 Bypass REVOKE DENY ... FROM PUBLIC privilege check.

DENY ... TO PUBLIC denies everyone, including whoever tries to revoke
it, via the "deny wins" merge at every scope (global, db, table, column,
routine). Allow REVOKE DENY ... FROM PUBLIC when the revoker can UPDATE
mysql.global_priv (same as hand-editing).

Assisted-by: Claude:claude-5-sonnet
05b4f34e58a7...
05b4f34e58a70f135d4b10ee998a1ff9732d24a0
Sergei Petrunia
MDEV-39499 Updates to derived-with-keys, window functions determining:

Unfinished review input.

The biggest change is making handle_single_part_rownumber() reuse
estimate_post_group_cardinality().

fails most of MDEV-39499's testcases in main/derived_opt.test,
not sure why.
05593f696223...
05593f696223e0dc631a2c1175c337111b35eadd
sjaakola
MDEV-37013 crash in applying FK cascade with virtual column

Added a simplified version of the Stefan Frye's test scenario
02a8d47e0e4c...
02a8d47e0e4c8fae16716b19db3bebce2b6cbf81
drrtuy
fix: MDEV-40386 disable MTR tests for MSAN builds b/c MSAN build is unstable.
021bd9024dcd...
021bd9024dcdda8b281d2694985199f1b68dea69
Oleksandr Byelkin
Merge fix
BuildBot (0.8.9) working for the MariaDB project.
Page built: Thu 06 Aug 2026 20:38:27 (UTC)