linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Paul Wise <pabs3@bonedaddy.net>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org
Subject: Re: [PATCH] core.5: explain the new situation with argument splitting
Date: Fri, 13 Sep 2019 15:02:05 +0200	[thread overview]
Message-ID: <b8907375-5bee-dfda-4836-d728920eede3@gmail.com> (raw)
In-Reply-To: <20190807014525.24825-1-pabs3@bonedaddy.net>

Hello Paul,

On 8/7/19 3:45 AM, Paul Wise wrote:
> It changed in Linux v5.3-rc3 commit 315c69261dd3 from
> splitting after template expansion to splitting beforehand.

Thanks. Patch applied.

Cheers,

Michael

> ---
>  man5/core.5 | 14 ++++++++++++++
>  1 file changed, 14 insertions(+)
> 
> diff --git a/man5/core.5 b/man5/core.5
> index d3efca3f8..ddc0352b8 100644
> --- a/man5/core.5
> +++ b/man5/core.5
> @@ -267,6 +267,20 @@ file.
>  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
> +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.
> +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
> +the executable name.
> +.PP
>  Instead of being written to a disk file, the core dump is given as
>  standard input to the program.
>  Note the following points:
> 


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

           reply	other threads:[~2019-09-13 13:02 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20190807014525.24825-1-pabs3@bonedaddy.net>]

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=b8907375-5bee-dfda-4836-d728920eede3@gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=pabs3@bonedaddy.net \
    /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;
as well as URLs for NNTP newsgroup(s).