From: Oleg Nesterov <oleg@redhat.com>
To: Emanuele Rocca <emanuele.rocca@arm.com>
Cc: linux-kernel@vger.kernel.org,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, Mark Brown <broonie@kernel.org>,
Jann Horn <jannh@google.com>
Subject: Re: [PATCH v3] pidfds: add coredump_code field to pidfd_info
Date: Mon, 23 Mar 2026 12:47:33 +0100 [thread overview]
Message-ID: <acEoVeBaP7bQRHLT@redhat.com> (raw)
In-Reply-To: <acBRj-DSCpqlKt6t@NH27D9T0LF>
On 03/22, Emanuele Rocca wrote:
>
> The struct pidfd_info currently exposes in a field called coredump_signal the
> signal number (si_signo) that triggered the dump (for example, 11 for SIGSEGV).
> However, it is also valuable to understand the reason why that signal was sent.
> This additional context is provided by the signal code (si_code), such as 2 for
> SEGV_ACCERR.
>
> Add a new field to struct pidfd_info called coredump_code with the value of
> si_code for the benefit of sysadmins who pipe core dumps to user-space programs
> for later analysis.
FWIW, the changes in pidfs.c and pidfd.h look good to me.
Acked-by: Oleg Nesterov <oleg@redhat.com>
next prev parent reply other threads:[~2026-03-23 11:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-22 20:31 [PATCH v3] pidfds: add coredump_code field to pidfd_info Emanuele Rocca
2026-03-23 11:47 ` Oleg Nesterov [this message]
2026-03-23 11:57 ` Christian Brauner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=acEoVeBaP7bQRHLT@redhat.com \
--to=oleg@redhat.com \
--cc=brauner@kernel.org \
--cc=broonie@kernel.org \
--cc=emanuele.rocca@arm.com \
--cc=jack@suse.cz \
--cc=jannh@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox