Re: gma500: mmu: unmap the correct address

[Daniel Vetter]

On Sun, Oct 29, 2017 at 01:55:12PM +0800, Pan Bian wrote:
> 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@xxxxxxx>

Makes sense, not sure this ever worked or how it ever worked, but oh well.

Applied to drm-misc-next for 4.16.
-Daniel

> ---
>  drivers/gpu/drm/gma500/mmu.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> 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;
> -- 
> 1.9.1
> 
> 
> _______________________________________________
> dri-devel mailing list
> dri-devel@xxxxxxxxxxxxxxxxxxxxx
> https://lists.freedesktop.org/mailman/listinfo/dri-devel

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch