From: Salvatore Bonaccorso <carnil@debian.org>
To: Jonathan Corbet <corbet@lwn.net>, Christian Brauner <brauner@kernel.org>
Cc: Luca Boccassi <luca.boccassi@gmail.com>,
Oleg Nesterov <oleg@redhat.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Salvatore Bonaccorso <carnil@debian.org>
Subject: [PATCH] Documentation/sysctl: coredump: add %F for pidfd number
Date: Thu, 12 Jun 2025 08:02:04 +0200 [thread overview]
Message-ID: <20250612060204.1159734-1-carnil@debian.org> (raw)
In commit b5325b2a270f ("coredump: hand a pidfd to the usermode coredump
helper") a new core_pattern specifier, %F, was added to provide a pidfs
to the usermode helper process referring to the crashed process.
Update the documentation to include the new core_pattern specifier.
Link: https://github.com/systemd/systemd/pull/37125
Link: https://lwn.net/Articles/1024160/
Signed-off-by: Salvatore Bonaccorso <carnil@debian.org>
---
Documentation/admin-guide/sysctl/kernel.rst | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/admin-guide/sysctl/kernel.rst b/Documentation/admin-guide/sysctl/kernel.rst
index dd49a89a62d3..f1b2ab219a08 100644
--- a/Documentation/admin-guide/sysctl/kernel.rst
+++ b/Documentation/admin-guide/sysctl/kernel.rst
@@ -177,6 +177,7 @@ core_pattern
%E executable path
%c maximum size of core file by resource limit RLIMIT_CORE
%C CPU the task ran on
+ %F pidfd number
%<OTHER> both are dropped
======== ==========================================
--
2.49.0
next reply other threads:[~2025-06-12 6:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 6:02 Salvatore Bonaccorso [this message]
2025-06-12 6:52 ` [PATCH] Documentation/sysctl: coredump: add %F for pidfd number Salvatore Bonaccorso
2025-06-21 20:18 ` Jonathan Corbet
2025-06-22 7:06 ` Salvatore Bonaccorso
2025-06-23 11:55 ` 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=20250612060204.1159734-1-carnil@debian.org \
--to=carnil@debian.org \
--cc=brauner@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.boccassi@gmail.com \
--cc=oleg@redhat.com \
/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