From: Jonathan Corbet <corbet@lwn.net>
To: Salvatore Bonaccorso <carnil@debian.org>,
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: Re: [PATCH] Documentation/sysctl: coredump: add %F for pidfd number
Date: Sat, 21 Jun 2025 14:18:38 -0600 [thread overview]
Message-ID: <87y0tkc0gx.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20250612060204.1159734-1-carnil@debian.org>
Salvatore Bonaccorso <carnil@debian.org> writes:
> 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(+)
Applied, thanks.
> FWIW, I was not sure if I should add a 'Fixes: b5325b2a270f
> ("coredump: hand a pidfd to the usermode coredump helper") to make
> sure that it get backported as well to the series where a backport of
> b5325b2a270f landed.
A Fixes tag is not sufficient to ensure that a patch is backported to
previous kernels - you must CC stable@vger.kernel.org to be sure. In
this case, it's a documentation tweak for a 6.16 change, so I don't
think there is a lot of urgency here.
Thanks,
jon
next prev parent reply other threads:[~2025-06-21 20:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 6:02 [PATCH] Documentation/sysctl: coredump: add %F for pidfd number Salvatore Bonaccorso
2025-06-12 6:52 ` Salvatore Bonaccorso
2025-06-21 20:18 ` Jonathan Corbet [this message]
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=87y0tkc0gx.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=brauner@kernel.org \
--cc=carnil@debian.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.