From: Pan Bian Date: Sun, 29 Oct 2017 05:55:12 +0000 (+0800) Subject: gma500: mmu: unmap the correct address X-Git-Tag: v4.19~298^2~45^2~795 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=39c9ce70f13a3127a8057e30b48a239bf08f7c8e;p=platform%2Fkernel%2Flinux-rpi3.git 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 Signed-off-by: Daniel Vetter Link: https://patchwork.freedesktop.org/patch/msgid/1509256512-5962-1-git-send-email-bianpan2016@163.com --- diff --git a/drivers/gpu/drm/gma500/mmu.c b/drivers/gpu/drm/gma500/mmu.c index 0eaf11c..ccb161c 100644 --- a/drivers/gpu/drm/gma500/mmu.c +++ b/drivers/gpu/drm/gma500/mmu.c @@ -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;