core.5: Minor tweaks to Paul Wise's patch

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2019-09-13 15:01:33 +02:00
parent a33adb814a
commit 344bbbd16a
1 changed files with 12 additions and 6 deletions

View File

@ -268,17 +268,23 @@ If the first character of this file is a pipe symbol (\fB|\fP),
then the remainder of the line is interpreted as the command-line for
a user-space program (or script) that is to be executed.
.PP
.\" 315c69261dd3fa12dbc830d4fa00d1fad98d3b03
Since kernel 5.3.0, the pipe template is split on spaces into an
argument list before the template parameters are expanded.
In earlier kernels the template parameters are expanded first and
Since kernel 5.3.0,
.\" commit 315c69261dd3fa12dbc830d4fa00d1fad98d3b03
the pipe template is split on spaces into an argument list
.I before
the template parameters are expanded.
In earlier kernels, the template parameters are expanded first and
the resulting string is split on spaces into an argument list.
This means that in earlier kernels executable names added by the
%e and %E template parameters could get split into multiple arguments.
.I %e
and
.I %E
template parameters could get split into multiple arguments.
So the core dump handler needs to put the executable names as the last
argument and ensure it joins all parts of the executable name using spaces.
Executable names with multiple spaces in them are not correctly represented
in earlier kernels so the core dump handler needs to use mechanisms to find
in earlier kernels,
meaning that the core dump handler needs to use mechanisms to find
the executable name.
.PP
Instead of being written to a disk file, the core dump is given as