[MDEV-29744] safe_mutex: Found wrong usage of mutex 'LOCK_commit_ordered' and 'LOCK_global_system_variables', or of mutex 'LOCK_global_system_variables' and 'LOCK_log', on setting max_binlog_size or binlog_checksum and START TRANSACTION - Jira

XML

Word

Printable

Details

Type: Bug
Status: In Review (View Workflow)
Priority: Critical
Resolution: Unresolved
Affects Version/s: 10.5, 10.6, 10.11, 11.1(EOL), 11.2, 11.4, 11.6, 11.7, 10.3(EOL), 10.4(EOL), 10.7(EOL), 10.8(EOL), 10.9(EOL), 10.10(EOL), 11.0(EOL), 11.3(EOL)
Fix Version/s: 10.5, 10.6, 10.11, 11.2, 11.4, 11.6
Component/s: Binary Protocol, Locking
Labels:
- affects-tests
- mutex

Description

# mysqld options required for replay: --log-bin

SET GLOBAL max_binlog_size=98304;  # A valid and arbritary setting

START TRANSACTION WITH CONSISTENT SNAPSHOT;

Leads to:

10.11.0 6ebdd3013a18b01dbecec76b870810329eb76586 (Debug)
safe_mutex: Found wrong usage of mutex 'LOCK_commit_ordered' and 'LOCK_global_system_variables'

And

# mysqld options required for replay: --log-bin

START TRANSACTION WITH CONSISTENT SNAPSHOT;

SET GLOBAL max_binlog_size=98304;  # A valid and arbritary setting

Leads to:

10.11.0 6ebdd3013a18b01dbecec76b870810329eb76586 (Debug)
safe_mutex: Found wrong usage of mutex 'LOCK_global_system_variables' and 'LOCK_log'

Bug confirmed present in:
MariaDB: 10.3.37 (dbg), 10.4.27 (dbg), 10.5.18 (dbg), 10.6.10 (dbg), 10.7.6 (dbg), 10.8.5 (dbg), 10.9.3 (dbg), 10.10.2 (dbg), 10.11.0 (dbg)

Attachments

Issue Links

is duplicated by

MDEV-35197 Wrong locking order of LOCK_log and LOCK_global_system_variables, potential deadlock of server

Closed

relates to

MDEV-35197 Wrong locking order of LOCK_log and LOCK_global_system_variables, potential deadlock of server

Closed

Activity

People

Assignee:: Sergei Golubchik

Reporter:: Roel Van de Paar

Votes:: 0 Vote for this issue

Watchers:: 6 Start watching this issue

Dates

Created:: 2022-10-08 06:06

Updated:: 6 days ago 18:35

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.