On Feb 20 09:43, Martin Pieuchot wrote: > On 20/02/23(Mon) 03:59, Renato Aguiar wrote: > > [...] > > I can't reproduce it anymore with this patch on 7.2-stable :) > > Thanks a lot for testing! Here's a better fix from Chuck Silvers. > That's what I believe we should commit. > > The idea is to prevent sibling from modifying the vm_map by marking > it as "busy" in msync(2) instead of holding the exclusive lock while > sleeping. This let siblings make progress and stop possible writers. > > Could you all guys confirm this also prevent the deadlock? Thanks!
I was not able to reproduce the deadlock using this patch.
