[MDEV-6532] MySQL Bug#72544 - Incorrect locking for global_query_id Created: 2014-08-05  Updated: 2014-08-05  Resolved: 2014-08-05

Status: Closed
Project: MariaDB Server
Component/s: None
Fix Version/s: 10.0.13

Type: Task Priority: Major
Reporter: Sergey Vojtovich Assignee: Michael Widenius
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
PartOf
is part of MDEV-6530 Examine and apply Power8 patches sugg... Closed

 Description   

global_query_id is atomic variable. Though it is protected by mutex in sp_head.cc:

mysql_mutex_lock(&LOCK_thread_count);
 
q= global_query_id;
 
mysql_mutex_unlock(&LOCK_thread_count);



 Comments   
Comment by Sergey Vojtovich [ 2014-08-05 ]

Fixed by Monty in 10.0.13:

revno: 4309
 
revision-id: monty@mariadb.org-20140730185826-ixp284l6b2aoha2t
 
parent: jplindst@mariadb.org-20140727054737-ieoohthuxc601q1a
 
committer: Michael Widenius <monty@mariadb.org>
 
branch nick: maria-10.0
 
timestamp: Wed 2014-07-30 21:58:26 +0300
 
message:
 
  Fixed wrong usage of global_query_id. (It's not protected by LOCK_thread_count)

Generated at Thu Feb 08 07:12:39 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.