Multi-master conflict resolving cause hanging or debug level assert

Resolving of multi-master conflicts can lead to situation when innodb kernel-mutex is tried to be locked twice by same THD:

130215 13:31:45 [Note] WSREP: BF kill (1, seqno: 1148093), victim: (1906) trx: 235097905
130215 13:31:45 [Note] WSREP: Aborting query: DELETE FROM comm01 WHERE p >= 1000
130215 13:31:45 [Note] WSREP: kill trx QUERY_EXEC for 235097905
130215 13:31:45 [Note] WSREP: kill query for: 1906
130215 13:31:45 InnoDB: Assertion failure in thread 140646447503104 in file sync0sync.ic line 207
InnoDB: Failing assertion: !mutex_own(mutex)

How to reproduce:
start two nodes and issue conflicting SQL load on both nodes