linux/tools/testing/selftests/coredump
Christian Brauner 32ae33f796
selftests/coredump: ignore ENOSPC errors
If we crash multiple processes at the same time we may run out of space.
Just ignore those errors. They're not actually all that relevant for the
test.

Link: https://patch.msgid.link/20251028-work-coredump-signal-v1-20-ca449b7b7aa0@kernel.org
Reviewed-by: Alexander Mikhalitsyn <aleksandr.mikhalitsyn@canonical.com>
Signed-off-by: Christian Brauner <brauner@kernel.org>
History 2025-11-04 22:04:57 +01:00
..
.gitignore selftests/coredump: split out coredump socket tests 2025-11-04 22:04:42 +01:00
config selftests/coredump: add coredump server selftests 2025-06-12 14:00:32 +02:00
coredump_socket_protocol_test.c selftests/coredump: ignore ENOSPC errors 2025-11-04 22:04:57 +01:00
coredump_socket_test.c selftests/coredump: ignore ENOSPC errors 2025-11-04 22:04:57 +01:00
coredump_test.h selftests/coredump: split out common helpers 2025-11-04 22:04:40 +01:00
coredump_test_helpers.c selftests/coredump: ignore ENOSPC errors 2025-11-04 22:04:57 +01:00
Makefile selftests/coredump: split out coredump socket tests 2025-11-04 22:04:42 +01:00
README.rst selftests: coredump: Add stackdump test 2025-01-04 10:12:18 +01:00
stackdump selftests: coredump: Add stackdump test 2025-01-04 10:12:18 +01:00
stackdump_test.c selftests/coredump: split out coredump socket tests 2025-11-04 22:04:42 +01:00

coredump selftest
=================

Background context
------------------

`coredump` is a feature which dumps a process's memory space when the process terminates
unexpectedly (e.g. due to segmentation fault), which can be useful for debugging. By default,
`coredump` dumps the memory to the file named `core`, but this behavior can be changed by writing a
different file name to `/proc/sys/kernel/core_pattern`. Furthermore, `coredump` can be piped to a
user-space program by writing the pipe symbol (`|`) followed by the command to be executed to
`/proc/sys/kernel/core_pattern`. For the full description, see `man 5 core`.

The piped user program may be interested in reading the stack pointers of the crashed process. The
crashed process's stack pointers can be read from `procfs`: it is the `kstkesp` field in
`/proc/$PID/stat`. See `man 5 proc` for all the details.

The problem
-----------
While a thread is active, the stack pointer is unsafe to read and therefore the `kstkesp` field
reads zero. But when the thread is dead (e.g. during a coredump), this field should have valid
value.

However, this was broken in the past and `kstkesp` was zero even during coredump:

* commit 0a1eb2d474ed ("fs/proc: Stop reporting eip and esp in /proc/PID/stat") changed kstkesp to
  always be zero

* commit fd7d56270b52 ("fs/proc: Report eip/esp in /prod/PID/stat for coredumping") fixed it for the
  coredumping thread. However, other threads in a coredumping process still had the problem.

* commit cb8f381f1613 ("fs/proc/array.c: allow reporting eip/esp for all coredumping threads") fixed
  for all threads in a coredumping process.

* commit 92307383082d ("coredump:  Don't perform any cleanups before dumping core") broke it again
  for the other threads in a coredumping process.

The problem has been fixed now, but considering the history, it may appear again in the future.

The goal of this test
---------------------
This test detects problem with reading `kstkesp` during coredump by doing the following:

#. Tell the kernel to execute the "stackdump" script when a coredump happens. This script
   reads the stack pointers of all threads of crashed processes.

#. Spawn a child process who creates some threads and then crashes.

#. Read the output from the "stackdump" script, and make sure all stack pointer values are
   non-zero.