summaryrefslogtreecommitdiff
path: root/crypto
diff options
context:
space:
mode:
authorDawei Li <dawei.li@shingroup.cn>2024-03-31 13:34:41 +0800
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2024-07-05 09:33:51 +0200
commit69f49527aea12c23b78fb3d0a421950bf44fb4e2 (patch)
tree4731a5cb0074202b5736378c309cf9c8441aae3b /crypto
parent724e7965af054079242b8d6f7e50ee226730a756 (diff)
downloadlinux-69f49527aea12c23b78fb3d0a421950bf44fb4e2.tar.gz
linux-69f49527aea12c23b78fb3d0a421950bf44fb4e2.tar.bz2
linux-69f49527aea12c23b78fb3d0a421950bf44fb4e2.zip
net/dpaa2: Avoid explicit cpumask var allocation on stack
[ Upstream commit d33fe1714a44ff540629b149d8fab4ac6967585c ] 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> Link: https://lore.kernel.org/r/20240331053441.1276826-3-dawei.li@shingroup.cn Signed-off-by: Jakub Kicinski <kuba@kernel.org> Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions