mbox series

[0/1] binfmt_elf, coredump: Log the reason of the failed core dumps

Message ID 20240617234133.1167523-1-romank@linux.microsoft.com (mailing list archive)
Headers show
Series binfmt_elf, coredump: Log the reason of the failed core dumps | expand

Message

Roman Kisel June 17, 2024, 11:41 p.m. UTC 
A powerful way to diagnose crashes is to analyze the core dump produced upon
the failure. Missing or malformed core dump files hinder these investigations.
I'd like to propose changes that add logging as to why the kernel would not
finish writing out the core dump file.

These changes don't attempt to turn the code into a state machine with the numerical
error codes. This is just the next step to not logging which is logging :).

Please let me know what is good, bad and ugly with these changes!

Signed-off-by: Roman Kisel <romank@linux.microsoft.com>

Roman Kisel (1):
  binfmt_elf, coredump: Log the reason of the failed core dumps

 fs/binfmt_elf.c          | 48 +++++++++++++++++++++-------
 fs/coredump.c            | 69 +++++++++++++++++++++++++++++++---------
 include/linux/coredump.h |  4 +--
 kernel/signal.c          |  5 ++-
 4 files changed, 96 insertions(+), 30 deletions(-)


base-commit: 831bcbcead6668ebf20b64fdb27518f1362ace3a