On 17/02/26(Tue) 21:01, Claudio Jeker wrote:
> [...]
> Doing a unlock, call function which locks then unlocks and on return lock
> the whole thing again is very error prone since after each unlock call a
> other caller may go in and modify the object you work on.

The bug is also triggered on single CPU machine so a mutex dance doesn't
matter.

Plus the mutex dance is done with the page owner lock held, which is
asserted to be held when the wired count is bumped.