The fix is described in the revision comments and the merge proposal for this bug (I wish Launchpad would make them visible somehow in the bug). I'll quote them here:
" Bug #692211: innodb_auto_lru_dump crashes if ib_lru_dump doesn't exist
Starting the server with a non-zero innodb_auto_lru_dump value could
crash the server if the dump file does not exist.
The problem was that the 'records' pointer was not initialized at the
start of buf_LRU_file_restore(). This could lead to calling ut_free()
with uninitialized value when the dump file is not found and further
execution of buf_LRU_file_restore() is therefore aborted.
The fix is described in the revision comments and the merge proposal for this bug (I wish Launchpad would make them visible somehow in the bug). I'll quote them here:
" auto_lru_ dump crashes if ib_lru_dump doesn't exist
Bug #692211: innodb_
Starting the server with a non-zero innodb_ auto_lru_ dump value could
crash the server if the dump file does not exist.
The problem was that the 'records' pointer was not initialized at the file_restore( ). This could lead to calling ut_free() file_restore( ) is therefore aborted.
start of buf_LRU_
with uninitialized value when the dump file is not found and further
execution of buf_LRU_
Fixed by initializing 'records' with NULL.
"