From: Andrew Morton <akpm@linux-foundation.org>
To: "La Monte H.P. Yarroll" <piggy@laurelnetworks.com>
Cc: linux-kernel@vger.kernel.org, Oleg Nesterov <oleg@tv-sign.ru>
Subject: Re: [PATCH] Provide control over core name even for multithreaded processes
Date: Tue, 2 Sep 2008 15:14:26 -0700 [thread overview]
Message-ID: <20080902151426.98935cd1.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080829152215.2cdb1438@kartuli>
On Fri, 29 Aug 2008 15:22:15 -0400
"La Monte H.P. Yarroll" <piggy@laurelnetworks.com> wrote:
> Our system explicitly sets core_pattern to force a relatively small
> limit on the number of different core dump names.
>
> Unfortunately, the kernel unconditionally appends .<tid> for
> multithreaded processes.
>
> The attached patch introduces "%T" to the core_pattern language, which
> expands to ".<tid>" for multithreaded processes. It then changes the
> default core_pattern to "core%T" replicating the current default
> behavior.
>
> Signed-off-by: La Monte H.P. Yarroll <piggy@laurelnetworks.com> 74-256740
>
> diff -Naur linux-2.6.26.3/Documentation/sysctl/kernel.txt linux-2.6.26.3-new/Documentation/sysctl/kernel.txt
> --- linux-2.6.26.3/Documentation/sysctl/kernel.txt 2008-08-20 14:11:37.000000000 -0400
> +++ linux-2.6.26.3-new/Documentation/sysctl/kernel.txt 2008-08-28 13:27:50.239325000 -0400
> @@ -88,7 +88,7 @@
> core_pattern:
>
> core_pattern is used to specify a core dumpfile pattern name.
> -. max length 128 characters; default value is "core"
> +. max length 128 characters; default value is "core%T"
> . core_pattern is used as a pattern template for the output filename;
> certain string patterns (beginning with '%') are substituted with
> their actual values.
> @@ -104,6 +104,7 @@
> %g gid
> %s signal number
> %t UNIX time of dump
> + %T .tgid or nothing if process is not threaded
> %h hostname
> %e executable filename
> %<OTHER> both are dropped
> diff -Naur linux-2.6.26.3/fs/exec.c linux-2.6.26.3-new/fs/exec.c
> --- linux-2.6.26.3/fs/exec.c 2008-08-20 14:11:37.000000000 -0400
> +++ linux-2.6.26.3-new/fs/exec.c 2008-08-28 13:46:57.919768000 -0400
> @@ -66,7 +66,7 @@
> #endif
>
> int core_uses_pid;
> -char core_pattern[CORENAME_MAX_SIZE] = "core";
> +char core_pattern[CORENAME_MAX_SIZE] = "core%T";
> int suid_dumpable = 0;
>
> /* The maximal length of core_pattern is also specified in sysctl.c */
> @@ -1415,7 +1415,7 @@
> case 'p':
> pid_in_pattern = 1;
> rc = snprintf(out_ptr, out_end - out_ptr,
> - "%d", task_tgid_vnr(current));
> + "%d", task_pid_vnr(current));
> if (rc > out_end - out_ptr)
> goto out;
> out_ptr += rc;
> @@ -1455,6 +1455,17 @@
> out_ptr += rc;
> break;
> }
> + /* Conditional tgid */
> + case 'T': {
> + if (atomic_read(¤t->mm->mm_users) != 1) {
> + rc = snprintf(out_ptr, out_end - out_ptr,
> + ".%d", task_tgid_vnr(current));
> + if (rc > out_end - out_ptr)
> + goto out;
> + out_ptr += rc;
> + }
> + break;
> + }
> /* hostname */
> case 'h':
> down_read(&uts_sem);
> @@ -1492,10 +1503,9 @@
> * 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 || atomic_read(¤t->mm->mm_users) != 1)) {
> + if (!ispipe && !pid_in_pattern && core_uses_pid) {
> rc = snprintf(out_ptr, out_end - out_ptr,
> - ".%d", task_tgid_vnr(current));
> + ".%d", current->pid);
> if (rc > out_end - out_ptr)
> goto out;
> out_ptr += rc;
Please review Oleg's
http://userweb.kernel.org/~akpm/mmotm/broken-out/coredump-format_corename-dont-append-%25pid-if-multi-threaded.patch,
which I have queued for 2.6.28.
next prev parent reply other threads:[~2008-09-02 22:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-29 19:22 La Monte H.P. Yarroll
2008-09-02 22:14 ` Andrew Morton [this message]
2008-09-03 13:50 ` La Monte Yarroll
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=20080902151426.98935cd1.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@tv-sign.ru \
--cc=piggy@laurelnetworks.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
Powered by JetHome