From: Emanuele Rocca <emanuele.rocca@arm.com>
To: linux-kernel@vger.kernel.org
Cc: 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>, Oleg Nesterov <oleg@redhat.com>
Subject: [PATCH v4 0/2] pidfds: add coredump_code field to pidfd_info
Date: Mon, 23 Mar 2026 14:00:45 +0100 [thread overview]
Message-ID: <acE5fYOgyVUYahIn@NH27D9T0LF> (raw)
This patchs series adds a new field called coredump_code to struct pidfd_info,
as well as the relevant selftests. Note that the coredump selftests are
currently not passing, and the following patch is needed to fix them:
https://lore.kernel.org/lkml/ab2kI0PI_Vk6bU88@NH27D9T0LF/
I have not included it in this series as it is not directly related to the
coredump_code changes.
v1: https://lore.kernel.org/lkml/ab29J6KsQm8Xg3LR@NH27D9T0LF/
v2: Add coredump_pad to struct pidfd_info to ensure the struct has the same
size on both 64 bit and 32 bit systems. The issue was spotted by the kernel
test robot.
https://lore.kernel.org/lkml/202603211842.JCwUVYTI-lkp@intel.com/
https://lore.kernel.org/lkml/ab68fUmCK4An1UH-@NH27D9T0LF/
v3: Sending as a new thread, same as v2 otherwise.
https://lore.kernel.org/lkml/acBRj-DSCpqlKt6t@NH27D9T0LF/
v4: Split kernel code from selftest code as suggested by Christian Brauner. Add
Acked-by: Oleg Nesterov to the commit adding the coredump_code field. Thanks!
https://lore.kernel.org/lkml/20260323-hochsehen-kurort-862912a1d7b5@brauner/
https://lore.kernel.org/lkml/acEoVeBaP7bQRHLT@redhat.com/
Emanuele Rocca (2):
pidfds: add coredump_code field to pidfd_info
selftests: check pidfd_info->coredump_code correctness
fs/pidfs.c | 12 ++++---
include/uapi/linux/pidfd.h | 4 +++
.../coredump/coredump_socket_protocol_test.c | 26 +++++++++++++++
.../selftests/coredump/coredump_socket_test.c | 32 +++++++++++++++++++
.../coredump/coredump_test_helpers.c | 4 +--
tools/testing/selftests/pidfd/pidfd.h | 5 +++
.../testing/selftests/pidfd/pidfd_info_test.c | 1 +
7 files changed, 78 insertions(+), 6 deletions(-)
--
2.47.3
next reply other threads:[~2026-03-23 13:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 13:00 Emanuele Rocca [this message]
2026-03-23 13:02 ` [PATCH v5 1/2] pidfds: add coredump_code field to pidfd_info Emanuele Rocca
2026-03-23 13:03 ` [PATCH v5 2/2] selftests: check pidfd_info->coredump_code correctness Emanuele Rocca
2026-03-26 14:42 ` [PATCH v4 0/2] pidfds: add coredump_code field to pidfd_info 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=acE5fYOgyVUYahIn@NH27D9T0LF \
--to=emanuele.rocca@arm.com \
--cc=brauner@kernel.org \
--cc=broonie@kernel.org \
--cc=jack@suse.cz \
--cc=jannh@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--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