pstore/ram: Fix failure-path memory leak in ramoops_init
authorKees Cook <keescook@chromium.org>
Fri, 28 Sep 2018 22:17:50 +0000 (15:17 -0700)
committerKees Cook <keescook@chromium.org>
Sun, 30 Sep 2018 17:15:41 +0000 (10:15 -0700)
commitbac6f6cda206ad7cbe0c73c35e494377ce9c4749
treebaf7c12f5ba0069ea47da897a8be25f43fc5ab2c
parent831b624df1b420c8f9281ed1307a8db23afb72df
pstore/ram: Fix failure-path memory leak in ramoops_init

As reported by nixiaoming, with some minor clarifications:

1) memory leak in ramoops_register_dummy():
   dummy_data = kzalloc(sizeof(*dummy_data), GFP_KERNEL);
   but no kfree() if platform_device_register_data() fails.

2) memory leak in ramoops_init():
   Missing platform_device_unregister(dummy) and kfree(dummy_data)
   if platform_driver_register(&ramoops_driver) fails.

I've clarified the purpose of ramoops_register_dummy(), and added a
common cleanup routine for all three failure paths to call.

Reported-by: nixiaoming <nixiaoming@huawei.com>
Cc: stable@vger.kernel.org
Cc: Anton Vorontsov <anton@enomsg.org>
Cc: Colin Cross <ccross@android.com>
Cc: Tony Luck <tony.luck@intel.com>
Cc: Joel Fernandes <joelaf@google.com>
Cc: Geliang Tang <geliangtang@gmail.com>
Signed-off-by: Kees Cook <keescook@chromium.org>
fs/pstore/ram.c