Bug #69413 description of bug#16268289 in the changelog may confuse people
Submitted: 6 Jun 2013 8:09 Modified: 27 Jun 2013 18:05
Reporter: zhai weixiang (OCA) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:5.6.12 OS:Any
Assigned to: Bugs System CPU Architecture:Any

[6 Jun 2013 8:09] zhai weixiang 
Description:
http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-12.html

InnoDB: When calling the lock_rec_block_validate() function after releasing the kernel mutex, there is a chance the lock might be invalid and result in a Valgrind error due to an invalid read on lock->index. This fix copies the lock->index when the kernel mutex is being held and passes the lock->index to lock_rec_block_validate(). (Bug #16268289)

Actually there isn't any kernel mutex in MySQL 5.6. 

We all know that :)

How to repeat:
read the doc   

Suggested fix:
don't  ctrl+c & ctrl+v ....
[6 Jun 2013 15:31] zhai weixiang 
It seems bug#16268289  is a NULL merge from 5.5...

http://bazaar.launchpad.net/~mysql/mysql-server/5.6/revision/4891

Committer: Aditya A
Date: 2013-03-13 06:15:07 UTC
mfrom: (2875.437.8 mysql-5.5)
Revision ID: aditya.a@oracle.com-20130313061507-o7eadmzwjvga9a76
Bug#16268289 LOCK_REC_VALIDATE_PAGE() MAY DEREFERENCE A POINTER TO A
             FREED LOCK
[Null Merge from 5.5]
[27 Jun 2013 18:05] Bugs System 
The changelog entry has been revised so that it only appears in the 5.5.32 changelog. Thank you for the catch and for the bug report.