[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <172291878808.3394314.1409314003306906435.b4-ty@kernel.org>
Date: Mon, 5 Aug 2024 21:33:12 -0700
From: Kees Cook <kees@...nel.org>
To: akpm@...ux-foundation.org,
apais@...ux.microsoft.com,
ardb@...nel.org,
bigeasy@...utronix.de,
brauner@...nel.org,
ebiederm@...ssion.com,
jack@...e.cz,
linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org,
linux-mm@...ck.org,
nagvijay@...rosoft.com,
oleg@...hat.com,
tandersen@...flix.com,
vincent.whitchurch@...s.com,
viro@...iv.linux.org.uk,
Kees Cook <kees@...nel.org>,
Roman Kisel <romank@...ux.microsoft.com>
Cc: apais@...rosoft.com,
benhill@...rosoft.com,
ssengar@...rosoft.com,
sunilmut@...rosoft.com,
vdso@...bites.dev
Subject: Re: [PATCH v3 0/2] binfmt_elf, coredump: Log the reason of the failed core dumps
On Thu, 18 Jul 2024 11:27:23 -0700, Roman Kisel wrote:
> 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.
>
> To help in diagnosing the user mode helper not writing out the entire coredump
> contents, the changes also log short statistics on the dump collection. I'd
> advocate for keeping this at the info level on these grounds.
>
> [...]
Applied to for-next/execve, thanks!
[1/2] coredump: Standartize and fix logging
https://git.kernel.org/kees/c/c114e9948c2b
[2/2] binfmt_elf, coredump: Log the reason of the failed core dumps
https://git.kernel.org/kees/c/fb97d2eb542f
Take care,
--
Kees Cook
Powered by blists - more mailing lists