gma500: mmu: unmap the correct address
The function kunmap_atomatic() is called on the same variable twice, i.e. pt->v. In the second call, its parameter should be variable v rather than pt->v. Signed-off-by: Pan Bian <bianpan2016@163.com> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch> Link: https://patchwork.freedesktop.org/patch/msgid/1509256512-5962-1-git-send-email-bianpan2016@163.com
This commit is contained in:
		
							parent
							
								
									4e7b212075
								
							
						
					
					
						commit
						39c9ce70f1
					
				| @ -395,7 +395,7 @@ static void psb_mmu_pt_unmap_unlock(struct psb_mmu_pt *pt) | ||||
| 			psb_mmu_clflush(pd->driver, (void *)&v[pt->index]); | ||||
| 			atomic_set(&pd->driver->needs_tlbflush, 1); | ||||
| 		} | ||||
| 		kunmap_atomic(pt->v); | ||||
| 		kunmap_atomic(v); | ||||
| 		spin_unlock(&pd->driver->lock); | ||||
| 		psb_mmu_free_pt(pt); | ||||
| 		return; | ||||
|  | ||||
		Loading…
	
		Reference in New Issue
	
	Block a user