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)
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>
Fri, 4 Feb 2022 17:55:43 +0000 (18:55 +0100)
commit38b16d6cfe54c820848bcfc999bc5e8a7da1cefb
treeb8f929837477c72fe027a6ced6bae1867a6bdd51
parent26291c54e111ff6ba87a164d85d4a4e134b7315c
thermal: int340x: Check for NULL after calling kmemdup()

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>
drivers/thermal/intel/int340x_thermal/int3400_thermal.c