Re: [PATCH] devm_memremap_release: fix memremap'd addr handling

From: Andrew Morton
Date: Tue Feb 16 2016 - 19:18:49 EST


On Tue, 16 Feb 2016 09:30:27 -0700 Toshi Kani <toshi.kani@xxxxxxx> wrote:

> The pmem driver calls devm_memremap() to map a persistent memory
> range. When the pmem driver is unloaded, this memremap'd range
> is not released.
>
> Fix devm_memremap_release() to handle a given memremap'd address
> properly.
>
> ...
>
> --- a/kernel/memremap.c
> +++ b/kernel/memremap.c
> @@ -114,7 +114,7 @@ EXPORT_SYMBOL(memunmap);
>
> static void devm_memremap_release(struct device *dev, void *res)
> {
> - memunmap(res);
> + memunmap(*(void **)res);
> }
>

Huh. So what happens? memunmap() decides it isn't a vmalloc address
and we leak a vma?

I'll add a cc:stable to this.