From: "Michael Kerrisk" <mtk.manpages@googlemail.com>
To: "Oleg Nesterov" <oleg@tv-sign.ru>
Cc: "Alan Cox" <alan@lxorguk.ukuu.org.uk>,
"Roland McGrath" <roland@redhat.com>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
andi@firstfloor.org
Subject: Re: [PATCH -mm] coredump: format_corename: don't append .%pid if multi-threaded
Date: Tue, 22 Jul 2008 14:21:20 +0200 [thread overview]
Message-ID: <cfd18e0f0807220521x5faea19bn1f545b23b84ead6a@mail.gmail.com> (raw)
In-Reply-To: <20080722121824.GB1383@tv-sign.ru>
On Tue, Jul 22, 2008 at 2:18 PM, Oleg Nesterov <oleg@tv-sign.ru> wrote:
> If the coredumping is multi-threaded, format_corename() appends .%pid
> to the corename. This was needed before the proper multi-thread core
> dump support, now all the threads in the mm go into a single unified
> core file.
>
> Remove this special case, it is not even documented and we have "%p"
> and core_uses_pid.
Hi Oleg,
I have not thought about this at any length, but one question that
jumps to mind: could this feature still be useful for LinuxThreads,
where each thread does indeed have a separate PID?
Cheers,
Michael
>
> Signed-off-by: Oleg Nesterov <oleg@tv-sign.ru>
>
> --- 26-rc2/fs/exec.c~FORMAT_CORENAME_NO_MT_PID 2008-07-22 15:42:15.000000000 +0400
> +++ 26-rc2/fs/exec.c 2008-07-22 15:46:04.000000000 +0400
> @@ -1373,7 +1373,7 @@ EXPORT_SYMBOL(set_binfmt);
> * name into corename, which must have space for at least
> * CORENAME_MAX_SIZE bytes plus one byte for the zero terminator.
> */
> -static int format_corename(char *corename, int nr_threads, long signr)
> +static int format_corename(char *corename, long signr)
> {
> const char *pat_ptr = core_pattern;
> int ispipe = (*pat_ptr == '|');
> @@ -1480,8 +1480,7 @@ static int format_corename(char *corenam
> * If core_pattern does not include a %p (as is the default)
> * and core_uses_pid is set, then .%pid will be appended to
> * the filename. Do not do this for piped commands. */
> - if (!ispipe && !pid_in_pattern
> - && (core_uses_pid || nr_threads)) {
> + if (!ispipe && !pid_in_pattern && core_uses_pid) {
> rc = snprintf(out_ptr, out_end - out_ptr,
> ".%d", task_tgid_vnr(current));
> if (rc > out_end - out_ptr)
> @@ -1745,7 +1744,7 @@ int do_coredump(long signr, int exit_cod
> * uses lock_kernel()
> */
> lock_kernel();
> - ispipe = format_corename(corename, retval, signr);
> + ispipe = format_corename(corename, signr);
> unlock_kernel();
> /*
> * Don't bother to check the RLIMIT_CORE value if core_pattern points
>
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
man-pages online: http://www.kernel.org/doc/man-pages/online_pages.html
Found a bug? http://www.kernel.org/doc/man-pages/reporting_bugs.html
next prev parent reply other threads:[~2008-07-22 12:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200807210137.m6L1bN0H011138@imap1.linux-foundation.org>
[not found] ` <20080721102940.666d733d@the-village.bc.nu>
[not found] ` <20080721210121.C5E741541A5@magilla.localdomain>
[not found] ` <20080721221416.6d4f9014@lxorguk.ukuu.org.uk>
[not found] ` <20080722113731.GA1383@tv-sign.ru>
2008-07-22 12:18 ` Oleg Nesterov
2008-07-22 12:21 ` Michael Kerrisk [this message]
2008-07-22 12:43 ` Oleg Nesterov
2008-07-22 12:47 ` Michael Kerrisk
2008-07-22 13:02 ` Oleg Nesterov
2008-07-22 14:46 ` Michael Kerrisk
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=cfd18e0f0807220521x5faea19bn1f545b23b84ead6a@mail.gmail.com \
--to=mtk.manpages@googlemail.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@tv-sign.ru \
--cc=roland@redhat.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
all inboxes | Powered by JetHome®