Dawei Li 9578df8a6b net/iucv: Avoid explicit cpumask var allocation on stack ...

[ Upstream commit be4e1304419c99a164b4c0e101c7c2a756b635b9 ]

For CONFIG_CPUMASK_OFFSTACK=y kernel, explicit allocation of cpumask
variable on stack is not recommended since it can cause potential stack
overflow.

Instead, kernel code should always use *cpumask_var API(s) to allocate
cpumask var in config-neutral way, leaving allocation strategy to
CONFIG_CPUMASK_OFFSTACK.

Use *cpumask_var API(s) to address it.

Signed-off-by: Dawei Li <dawei.li@shingroup.cn>
Reviewed-by: Alexandra Winter <wintera@linux.ibm.com>
Link: https://lore.kernel.org/r/20240331053441.1276826-2-dawei.li@shingroup.cn
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
(cherry picked from commit 2b085521be5292016097b5e7ca81b26be3f7098d)
Signed-off-by: Vegard Nossum <vegard.nossum@oracle.com>

2024-08-08 15:52:20 +00:00

..

af_iucv.c

net/af_iucv: clean up a try_then_request_module()

2024-03-08 08:21:37 +00:00

iucv.c

net/iucv: Avoid explicit cpumask var allocation on stack

2024-08-08 15:52:20 +00:00

Kconfig

…

Makefile

…