linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Lepton Wu <ytht.net@gmail.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v2] coredump: Add %f for executable file name.
Date: Tue, 30 Jun 2020 19:26:31 -0700	[thread overview]
Message-ID: <20200630192631.612f79b6226b36630c1429de@linux-foundation.org> (raw)
In-Reply-To: <20200627042303.1216506-1-ytht.net@gmail.com>

On Fri, 26 Jun 2020 21:23:03 -0700 Lepton Wu <ytht.net@gmail.com> wrote:

> The document reads "%e" should be executable file name while actually
> it could be changed by things like pr_ctl PR_SET_NAME. We can't really
> change the behavior of "%e" for now, so introduce a new "%f" for the
> real executable file name.

Please explain (in as much detail as possible) why you believe the
kernel should be changed in this way.

  reply	other threads:[~2020-07-01  2:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-27  4:01 [PATCH] coredump: Add %f for executable file name Lepton Wu
2020-06-27  4:23 ` [PATCH v2] " Lepton Wu
2020-07-01  2:26   ` Andrew Morton [this message]
2020-07-01  3:14     ` [PATCH v3] coredump: Add %f for executable filename Lepton Wu

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=20200630192631.612f79b6226b36630c1429de@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).