public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Emanuele Rocca <emanuele.rocca@arm.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org, Lepton Wu <ytht.net@gmail.com>,
	Oleksandr Natalenko <oleksandr@natalenko.name>
Subject: [PATCH] core.5: document the %f and %C core_pattern specifiers
Date: Fri, 13 Mar 2026 20:15:54 +0100	[thread overview]
Message-ID: <abRiap_UrhFzNxPs@NH27D9T0LF> (raw)

Whilst going through the relevant kernel code in fs/coredump.c, I noticed that
two core pattern specifiers supported by Linux are missing from man5/core.5.
Document them now.

Signed-off-by: Emanuele Rocca <emanuele.rocca@arm.com>
---
 man/man5/core.5 | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/man/man5/core.5 b/man/man5/core.5
index 8c26aa07e..4da5819b6 100644
--- a/man/man5/core.5
+++ b/man/man5/core.5
@@ -154,6 +154,11 @@ A single % character.
 %c
 Core file size soft resource limit of crashing process (since Linux 2.6.24).
 .TP
+%C
+CPU the task ran on
+.\" commit 8603b6f58637ce196d68f7749633ea81af196d66
+(since Linux 6.2).
+.TP
 %d
 .\" Added in git commit 12a2b4b2241e318b4f6df31228e4272d2c2968a1
 Dump mode\[em]same as value returned by
@@ -179,6 +184,11 @@ Pathname of executable,
 with slashes (\[aq]/\[aq]) replaced by exclamation marks (\[aq]!\[aq])
 (since Linux 3.0).
 .TP
+%f
+Actual filename of executable, which may differ from %e
+.\" commit f38c85f1ba6902e4e2e2bf1b84edf065a904cdeb
+(since Linux 5.9).
+.TP
 %F
 PIDFD of dumped process
 .\" commit b5325b2a270fcaf7b2a9a0f23d422ca8a5a8bdea
-- 
2.47.3


             reply	other threads:[~2026-03-13 19:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-13 19:15 Emanuele Rocca [this message]
2026-03-13 20:29 ` [PATCH] core.5: document the %f and %C core_pattern specifiers Oleksandr Natalenko
2026-03-13 20:51   ` lepton
2026-03-16  0:05     ` Alejandro Colomar

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=abRiap_UrhFzNxPs@NH27D9T0LF \
    --to=emanuele.rocca@arm.com \
    --cc=alx@kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=oleksandr@natalenko.name \
    --cc=ytht.net@gmail.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