Bug #29431 killing an insert delayed thread causes crash
Submitted: 28 Jun 2007 22:01 Modified: 27 Jul 2007 5:09
Reporter: Shane Bester (Platinum Quality Contributor) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Locking Severity:S3 (Non-critical)
Version:4.1,5.0.46,5.1 OS:Any
Assigned to: Konstantin Osipov CPU Architecture:Any
Tags: crash, hang, insert delayed, stack overrun

[28 Jun 2007 22:01] Shane Bester 
Description:
seen mysqld process die after a thread sent KILL <id> to the server and <id> happened to be some insert delayed query running.

mostly there's no stack trace in the logs because it appears mysqld was killed by kernel.

once, I saw some out of memory messages.

How to repeat:
will make a testcase later.

Suggested fix:
.
[28 Jun 2007 22:52] MySQL Verification Team 
there's a massive stack overrun happening in this crash. even debug build in debugger didn't catch a stack trace.
[28 Jun 2007 22:54] MySQL Verification Team 
testcase. see top of fille for user, host, gcc compile example

Attachment: bug29431.c (text/plain), 8.08 KiB.
[28 Jun 2007 22:57] MySQL Verification Team 
some testcase output, and error log

Attachment: bug29431_testcase_output.txt (text/plain), 4.82 KiB.
[28 Jun 2007 23:10] MySQL Verification Team 
some notes.  i ran debug server which crashed much quicker than release server.  5.0.36-enterprise-gpl-glib23 did crash, after a few minutes.  debug 5.0.46 crashes much quicker.

run the server to allow fast connections:

mysqld_safe --skip-grant-tables --skip-name-resolve --skip-innodb --back_log=10000
[28 Jun 2007 23:23] MySQL Verification Team 
i couldn't crash 5.1.20, but all threads got hanged

Attachment: bug29431_hang_on_5.1.20.txt (text/plain), 4.58 KiB.
[17 Jul 2007 23:01] Konstantin Osipov 
Also repeatable in 4.1
[18 Jul 2007 23:13] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/31144

ChangeSet@1.2533, 2007-07-19 03:13:10+04:00, kostja@bodhi.(none) +1 -0
  A fix for Bug#29431 killing an insert delayed thread causes crash
  No test case, since the bug requires a stress case with 30 INSERT DELAYED
  threads and 1 killer thread to repeat. The patch is verified
  manually.
  
  The server that is running DELAYED inserts would deadlock itself
  or crash under high load if some of the delayed threads were KILLed
  in the meanwhile.
  
  The fix is to change internal lock acquisition order of delayed inserts
  subsystem and to ensure that
  Delayed_insert::table_list::db does not point to volatile memory in some 
  cases.
  For details, please see a comment for sql_insert.cc.
[18 Jul 2007 23:28] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/31145

ChangeSet@1.2533, 2007-07-19 03:28:47+04:00, kostja@bodhi.(none) +1 -0
  A fix for Bug#29431 killing an insert delayed thread causes crash
  No test case, since the bug requires a stress case with 30 INSERT DELAYED
  threads and 1 killer thread to repeat. The patch is verified
  manually.
  
  The server that is running DELAYED inserts would deadlock itself
  or crash under high load if some of the delayed threads were KILLed
  in the meanwhile.
  
  The fix is to change internal lock acquisition order of delayed inserts
  subsystem and to ensure that
  Delayed_insert::table_list::db does not point to volatile memory in some 
  cases.
  For details, please see a comment for sql_insert.cc.
[19 Jul 2007 15:29] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/31175

ChangeSet@1.2533, 2007-07-19 19:28:00+04:00, kostja@bodhi.(none) +1 -0
  A fix for Bug#29431 killing an insert delayed thread causes crash
  No test case, since the bug requires a stress case with 30 INSERT DELAYED
  threads and 1 killer thread to repeat. The patch is verified
  manually.
  Review fixes.
  
  The server that is running DELAYED inserts would deadlock itself
  or crash under high load if some of the delayed threads were KILLed
  in the meanwhile.
  
  The fix is to change internal lock acquisition order of delayed inserts
  subsystem and to ensure that
  Delayed_insert::table_list::db does not point to volatile memory in some 
  cases.
  For details, please see a comment for sql_insert.cc.
[19 Jul 2007 15:40] Konstantin Osipov 
Queued into 5.0-runtime
[19 Jul 2007 17:10] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/31184

ChangeSet@1.2559, 2007-07-19 21:10:19+04:00, kostja@bodhi.(none) +1 -0
  A follow-up fix for Bug#29431 "killing an insert delayed thread causes 
  crash" in 5.1
[25 Jul 2007 8:47] Bugs System 
Pushed into 5.0.48
[25 Jul 2007 8:48] Bugs System 
Pushed into 5.1.21-beta
[27 Jul 2007 5:09] Paul DuBois 
Noted in 5.0.48, 5.1.21 changelogs.

Killing an INSERT DELAYED thread caused a server crash.