From: Earl Chew <echew@ixiacom.com>
To: <jslaby@suse.cz>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] coredump: escape / in hostname and comm
Date: Tue, 30 Aug 2011 08:21:44 -0700 [thread overview]
Message-ID: <4E5D0008.5090504@ixiacom.com> (raw)
In-Reply-To: <1307457010-7241-2-git-send-email-jslaby@suse.cz>
Jiri,
I would like to suggest that both '%e' and '%E' use current->group_leader->comm
instead of just current->comm.
Using plain current->comm gets strange effects when threads within a process
start naming themselves using PR_SET_NAME (or its pthread_setname_np() equivalent).
Earl
next prev parent reply other threads:[~2011-08-30 15:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 14:30 [PATCH v2 1/2] coredump: use task comm instead of (unknown) Jiri Slaby
2011-06-07 14:30 ` [PATCH v2 2/2] coredump: escape / in hostname and comm Jiri Slaby
2011-08-30 15:21 ` Earl Chew [this message]
2011-06-07 18:16 ` [PATCH v2 1/2] coredump: use task comm instead of (unknown) Oleg Nesterov
2011-06-07 18:30 ` Jiri Slaby
2011-06-08 19:26 ` Oleg Nesterov
2011-06-07 18:35 ` [PATCH] do_coredump: fix the "ispipe" error check Oleg Nesterov
2011-06-07 19:00 ` Jiri Slaby
2011-06-07 19:07 ` Neil Horman
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=4E5D0008.5090504@ixiacom.com \
--to=echew@ixiacom.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
/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