diff options
author | Vladimir Oltean <[email protected]> | 2024-07-14 01:53:32 +0300 |
---|---|---|
committer | Jakub Kicinski <[email protected]> | 2024-07-14 20:26:16 -0700 |
commit | 555a05d84ca2c587e2d4777006e2c2fb3dfbd91d (patch) | |
tree | 70eb909f21fbedec14e57676d9deabc90df162ab /tools/perf/util/scripting-engines/trace-event-python.c | |
parent | 62fdd1708fcb3e1c58d21221bf0861a8b1975f90 (diff) |
net: dpaa: avoid on-stack arrays of NR_CPUS elements
The dpaa-eth driver is written for PowerPC and Arm SoCs which have 1-24
CPUs. It depends on CONFIG_NR_CPUS having a reasonably small value in
Kconfig. Otherwise, there are 2 functions which allocate on-stack arrays
of NR_CPUS elements, and these can quickly explode in size, leading to
warnings such as:
drivers/net/ethernet/freescale/dpaa/dpaa_eth.c:3280:12: warning:
stack frame size (16664) exceeds limit (2048) in 'dpaa_eth_probe' [-Wframe-larger-than]
The problem is twofold:
- Reducing the array size to the boot-time num_possible_cpus() (rather
than the compile-time NR_CPUS) creates a variable-length array,
which should be avoided in the Linux kernel.
- Using NR_CPUS as an array size makes the driver blow up in stack
consumption with generic, as opposed to hand-crafted, .config files.
A simple solution is to use dynamic allocation for num_possible_cpus()
elements (aka a small number determined at runtime).
Link: https://lore.kernel.org/all/[email protected]/
Signed-off-by: Vladimir Oltean <[email protected]>
Reviewed-by: Breno Leitao <[email protected]>
Acked-by: Madalin Bucur <[email protected]>
Link: https://patch.msgid.link/[email protected]
Signed-off-by: Jakub Kicinski <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions