diff options
| author | Arnd Bergmann <arnd@arndb.de> | 2026-10-16 21:46:39 +0200 |
|---|---|---|
| committer | Christian Brauner <brauner@kernel.org> | 2026-10-22 18:48:38 +0200 |
| commit | 86b318cd830d2f1f8c3f83b9f1b3084c8c2ba6f1 (patch) | |
| tree | 0d2b8699c4eccc056235e244cdc828bf36ea6d9d /tools/lib/python/kdoc/python_version.py | |
| parent | ad0312e1decd40d18e0e75de96c9c52013ec05be (diff) | |
coredump: reduce stack usage in vfs_coredump
A recent patch changed the coredump code in mostly harmless ways,
but after this I get a very high stack usage in one function
that was benign before:
fs/coredump.c: In function 'vfs_coredump':
fs/coredump.c:1313:1: error: the frame size of 1872 bytes is larger than 1536 bytes [-Werror=frame-larger-than=]
This happens reproducibly every couple of randconfig builds on
s390 with gcc-16 and seems to be caused by kasan checks causing
local variables to be spilled to the stack.
Marking the do_coredump function as noinline_for_stack avoids
the problem here, instead I get only 464 and 672 bytes in
the worst case for vfs_coredump and do_coredump, respectively.
Fixes: 3209535cd39e ("pidfs: record the coredump on the dumping thread's pid too")
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Link: https://patch.msgid.link/20261016194650.1580988-1-arnd@kernel.org
Signed-off-by: Christian Brauner (Amutable) <brauner@kernel.org>
Diffstat (limited to 'tools/lib/python/kdoc/python_version.py')
0 files changed, 0 insertions, 0 deletions
