List:Commits« Previous MessageNext Message »
From:rsomla Date:February 27 2007 7:38pm
Subject:bk commit into 5.0 tree (rafal:1.2426)
View as plain text  
Below is the list of changes that have just been committed into a local
5.0 repository of rafal. When rafal does a push these changes will
be propagated to the main repository and, within 24 hours after the
push, to the public repository.
For information on how to access the public repository
see http://dev.mysql.com/doc/mysql/en/installing-source-tree.html

ChangeSet@stripped, 2007-02-27 19:38:39+01:00, rafal@quant.(none) +2 -0
  Merge quant.(none):/ext/mysql/bkroot/mysql-5.0-rpl
  into  quant.(none):/ext/mysql/bk/mysql-5.0-bug25306
  MERGE: 1.2341.72.6

  sql/slave.cc@stripped, 2007-02-27 19:38:29+01:00, rafal@quant.(none) +0 -0
    Auto merged
    MERGE: 1.286.2.2

  sql/sql_repl.cc@stripped, 2007-02-27 19:38:30+01:00, rafal@quant.(none) +0 -0
    Auto merged
    MERGE: 1.155.1.1

# This is a BitKeeper patch.  What follows are the unified diffs for the
# set of deltas contained in the patch.  The rest of the patch, the part
# that BitKeeper cares about, is below these diffs.
# User:	rafal
# Host:	quant.(none)
# Root:	/ext/mysql/bk/mysql-5.0-bug25306/RESYNC

--- 1.292/sql/slave.cc	2007-02-27 19:38:48 +01:00
+++ 1.293/sql/slave.cc	2007-02-27 19:38:48 +01:00
@@ -3759,8 +3759,13 @@
   mi->abort_slave= 0;
   mi->slave_running= 0;
   mi->io_thd= 0;
-  pthread_mutex_unlock(&mi->run_lock);
+  /*
+    Note: the order of the two following calls (first broadcast, then unlock)
+    is important. Otherwise a killer_thread can execute between the calls and
+    delete the mi structure leading to a crash! (see BUG#25306 for details)
+   */ 
   pthread_cond_broadcast(&mi->stop_cond);       // tell the world we are done
+  pthread_mutex_unlock(&mi->run_lock);
 #ifndef DBUG_OFF
   if (abort_slave_event_count && !events_till_abort)
     goto slave_begin;
@@ -3978,8 +3983,13 @@
   THD_CHECK_SENTRY(thd);
   delete thd;
   pthread_mutex_unlock(&LOCK_thread_count);
-  pthread_cond_broadcast(&rli->stop_cond);
 
+ /*
+  Note: the order of the broadcast and unlock calls below (first broadcast, then unlock)
+  is important. Otherwise a killer_thread can execute between the calls and
+  delete the mi structure leading to a crash! (see BUG#25306 for details)
+ */ 
+  pthread_cond_broadcast(&rli->stop_cond);
 #ifndef DBUG_OFF
   /*
     Bug #19938 Valgrind error (race) in handle_slave_sql()
@@ -3987,9 +3997,8 @@
   */
   const int eta= rli->events_till_abort;
 #endif
-
-  // tell the world we are done
-  pthread_mutex_unlock(&rli->run_lock);
+  pthread_mutex_unlock(&rli->run_lock);  // tell the world we are done
+  
 #ifndef DBUG_OFF // TODO: reconsider the code below
   if (abort_slave_event_count && !eta)
     goto slave_begin;

--- 1.156/sql/sql_repl.cc	2007-02-27 19:38:48 +01:00
+++ 1.157/sql/sql_repl.cc	2007-02-27 19:38:48 +01:00
@@ -882,12 +882,14 @@
 
 int stop_slave(THD* thd, MASTER_INFO* mi, bool net_report )
 {
+  DBUG_ENTER("stop_slave");
+  
   int slave_errno;
   if (!thd)
     thd = current_thd;
 
   if (check_access(thd, SUPER_ACL, any_db,0,0,0,0))
-    return 1;
+    DBUG_RETURN(1);
   thd->proc_info = "Killing slave";
   int thread_mask;
   lock_slave_threads(mi);
@@ -921,12 +923,12 @@
   {
     if (net_report)
       my_message(slave_errno, ER(slave_errno), MYF(0));
-    return 1;
+    DBUG_RETURN(1);
   }
   else if (net_report)
     send_ok(thd);
 
-  return 0;
+  DBUG_RETURN(0);
 }
 
 
Thread
bk commit into 5.0 tree (rafal:1.2426)rsomla27 Feb