summaryrefslogtreecommitdiff
path: root/fs/ntfs/malloc.h
diff options
context:
space:
mode:
authorKees Cook <keescook@chromium.org>2018-09-29 01:17:50 +0300
committerBen Hutchings <ben@decadent.org.uk>2018-12-17 01:09:31 +0300
commit1ed20af2554ce6f3b38f24f20a1667e6e6ebd961 (patch)
tree5d5c8dfe89fdd715ea115b5b4093002c1fa7bc1a /fs/ntfs/malloc.h
parent699f809e73317a968576d73e0a0d6661cdedc09e (diff)
downloadlinux-1ed20af2554ce6f3b38f24f20a1667e6e6ebd961.tar.xz
pstore/ram: Fix failure-path memory leak in ramoops_init
commit bac6f6cda206ad7cbe0c73c35e494377ce9c4749 upstream. 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: 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> [bwh: Backported to 3.16: adjust context] Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Diffstat (limited to 'fs/ntfs/malloc.h')
0 files changed, 0 insertions, 0 deletions