On Wed, Dec 18, 2024 at 09:36:42AM -0800, Suren Baghdasaryan wrote: > > You will not. vms_complete_munmap_vmas() will call remove_vma() to > > remove PTEs IIRC, and if you do start_write() and detach() before > > dropping mmap_lock_write, you should be good. > > Ok, I think we will have to move mmap_write_downgrade() inside > vms_complete_munmap_vmas() to be called after remove_vma(). > vms_clear_ptes() is using vmas, so we can't move remove_vma() before > mmap_write_downgrade(). Why ?! vms_clear_ptes() and remove_vma() are fine where they are -- there is no concurrency left at this point. Note that by doing vma_start_write() inside vms_complete_munmap_vmas(), which is *after* the vmas have been unhooked from the mm, you wait for any concurrent user to go away. And since they're unhooked, there can't be any new users. So you're the one and only user left, and code is fine the way it is.
