Comment 1 for bug 381893

Basically, the level of the new mutex/rw_lock are set SYNC_NO_ORDER_CHECK by split_buf_pool_mutex.patch .
So, currently, UNIV_SYNC_DEBUG is useless mode. (It cannot check the new latch orders).

This assertion is caused by changing latch order between block->mutex and buf_pool->mutex.
The patched buf_pool->mutex protects only aio flags.

Do you want to make the UNIV_SYNC_DEBUG sense?
The latching order is different from XtraDB's patch.
So,,, I need time to reinvestigation to make sense.

Thank you