linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: menglong8.dong@gmail.com
Cc: pabs3@bonedaddy.net, viro@zeniv.linux.org.uk,
	nhorman@tuxdriver.com, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Menglong Dong <dong.menglong@zte.com.cn>
Subject: Re: [PATCH] coredump: fix core_pattern parse error
Date: Mon, 23 Nov 2020 20:06:36 -0800	[thread overview]
Message-ID: <20201123200636.2dbbf127e7cd75b4022bd75f@linux-foundation.org> (raw)
In-Reply-To: <5fb62870.1c69fb81.8ef5d.af76@mx.google.com>

On Thu, 19 Nov 2020 03:08:43 -0500 menglong8.dong@gmail.com wrote:

> From: Menglong Dong <dong.menglong@zte.com.cn>
> 
> 'format_corename()' will splite 'core_pattern' on spaces when it
> is in pipe mode, and take helper_argv[0] as the path to usermode
> executable.
> 
> It works fine in most cases. However, if there is a space between
> '|' and '/file/path', such as
> '| /usr/lib/systemd/systemd-coredump %P %u %g',
> helper_argv[0] will be parsed as '', and users will get a
> 'Core dump to | disabled'.
> 
> It is not friendly to users, as the pattern above was valid previously.
> Fix this by ignoring the spaces between '|' and '/file/path'.
> 
> ...
>
> --- a/fs/coredump.c
> +++ b/fs/coredump.c
> @@ -229,7 +229,8 @@ static int format_corename(struct core_name *cn, struct coredump_params *cprm,
>  		 */
>  		if (ispipe) {
>  			if (isspace(*pat_ptr)) {
> -				was_space = true;
> +				if (cn->used != 0)
> +					was_space = true;
>  				pat_ptr++;
>  				continue;
>  			} else if (was_space) {

Looks good to me.  It's been a bit more than a year, but I'll add a
cc:stable to this so that the earlier kernels get the fix.


      reply	other threads:[~2020-11-24  4:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-19  8:08 [PATCH] coredump: fix core_pattern parse error menglong8.dong
2020-11-24  4:06 ` Andrew Morton [this message]

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=20201123200636.2dbbf127e7cd75b4022bd75f@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=dong.menglong@zte.com.cn \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=menglong8.dong@gmail.com \
    --cc=nhorman@tuxdriver.com \
    --cc=pabs3@bonedaddy.net \
    --cc=viro@zeniv.linux.org.uk \
    /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).