ramoops: use persistent_ram_free() instead of kfree() for freeing prz

toyooka · kees · commit e976e56423dc · 2016-08-05T11:21:46.000-07:00
persistent_ram_zone(=prz) structures are allocated by persistent_ram_new(),
which includes vmap() or ioremap(). But they are currently freed by
kfree(). This uses persistent_ram_free() for correct this asymmetry usage.

Signed-off-by: Hiraku Toyooka &lt;hiraku.toyooka.gu@hitachi.com&gt;
Signed-off-by: Nobuhiro Iwamatsu &lt;nobuhiro.iwamatsu.kw@hitachi.com&gt;
Cc: Mark Salyzyn &lt;salyzyn@android.com&gt;
Cc: Seiji Aguchi &lt;seiji.aguchi.tr@hitachi.com&gt;
Signed-off-by: Kees Cook &lt;keescook@chromium.org&gt;
diff --git a/fs/pstore/ram.c b/fs/pstore/ram.c
@@ -643,11 +643,11 @@ static int ramoops_probe(struct platform_device *pdev)
 	kfree(cxt->pstore.buf);
 fail_clear:
 	cxt->pstore.bufsize = 0;
-	kfree(cxt->mprz);
+	persistent_ram_free(cxt->mprz);
 fail_init_mprz:
-	kfree(cxt->fprz);
+	persistent_ram_free(cxt->fprz);
 fail_init_fprz:
-	kfree(cxt->cprz);
+	persistent_ram_free(cxt->cprz);
 fail_init_cprz:
 	ramoops_free_przs(cxt);
 fail_out:
