thermal: int340x: Check for NULL after calling kmemdup()
authorJiasheng Jiang <jiasheng@iscas.ac.cn>
Wed, 26 Jan 2022 01:48:53 +0000 (09:48 +0800)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Fri, 8 Apr 2022 12:23:05 +0000 (14:23 +0200)
commit9ada174f47b31f7c9b24c0da55b2b649aec7fafb
tree74295e2c3fd2dedc3e0fbc1cf28db5d4f9ceade2
parent486d4c18f207eef95459f3258238eab418c3c4e9
thermal: int340x: Check for NULL after calling kmemdup()

[ Upstream commit 38b16d6cfe54c820848bcfc999bc5e8a7da1cefb ]

As the potential failure of the allocation, kmemdup() may return NULL.

Then, 'bin_attr_data_vault.private' will be NULL, but
'bin_attr_data_vault.size' is not 0, which is not consistent.

Therefore, it is better to check the return value of kmemdup() to
avoid the confusion.

Fixes: 0ba13c763aac ("thermal/int340x_thermal: Export GDDV")
Signed-off-by: Jiasheng Jiang <jiasheng@iscas.ac.cn>
[ rjw: Subject and changelog edits ]
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
drivers/thermal/intel/int340x_thermal/int3400_thermal.c