search for: __vm_munmap

Displaying 3 results from an estimated 3 matches for "__vm_munmap".

Did you mean: __do_munmap
2020 Jan 09
1
[BUG] nouveau lockdep splat
...26] nouveau_svmm_invalidate_range_start+0x71/0x110 [nouveau] [ 98.466593] __mmu_notifier_invalidate_range_start+0x25c/0x320 [ 98.473031] unmap_vmas+0x10c/0x200 [ 98.477130] unmap_region+0x1a4/0x240 [ 98.481410] __do_munmap+0x3e0/0x750 [ 98.485535] __vm_munmap+0xbc/0x130 [ 98.489599] __x64_sys_munmap+0x3c/0x50 [ 98.493951] do_syscall_64+0x68/0x280 [ 98.498162] entry_SYSCALL_64_after_hwframe+0x49/0xbe [ 98.503778] [ 98.503778] -> #2 (mmu_notifier_invalidate_range_start){+.+.}: [ 98.511084] __mmu_notifier_registe...
2020 Oct 23
0
kvm+nouveau induced lockdep gripe
...0x50 [nouveau] [ 70.136302] ttm_bo_cleanup_memtype_use+0x3e/0x60 [ttm] [ 70.136310] ttm_bo_release+0x29c/0x600 [ttm] [ 70.136317] ttm_bo_vm_close+0x15/0x30 [ttm] [ 70.136324] remove_vma+0x3e/0x70 [ 70.136329] __do_munmap+0x2b7/0x4f0 [ 70.136333] __vm_munmap+0x5b/0xa0 [ 70.136338] __x64_sys_munmap+0x27/0x30 [ 70.136343] do_syscall_64+0x33/0x40 [ 70.136349] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 70.136354] -> #0 (&mm->mmap_lock#2){++++}-{3:3}: [ 70.136365] __lock_acquire+0x149d/0x1a70 [...
2020 Oct 24
1
kvm+nouveau induced lockdep gripe
...] Looks like we can break the lock chain by moving ttm bo's release method out of mmap_lock, see diff below. > [ 70.136317] ttm_bo_vm_close+0x15/0x30 [ttm] > [ 70.136324] remove_vma+0x3e/0x70 > [ 70.136329] __do_munmap+0x2b7/0x4f0 > [ 70.136333] __vm_munmap+0x5b/0xa0 > [ 70.136338] __x64_sys_munmap+0x27/0x30 > [ 70.136343] do_syscall_64+0x33/0x40 > [ 70.136349] entry_SYSCALL_64_after_hwframe+0x44/0xa9 > [ 70.136354] > -> #0 (&mm->mmap_lock#2){++++}-{3:3}: > [ 70.136365] _...