From: La Monte Yarroll <piggy@laurelnetworks.com>
To: Andrew Morton <akpm@linux-foundation.org>
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: Wed, 3 Sep 2008 09:50:36 -0400 [thread overview]
Message-ID: <20080903095036.0331de10@kartuli> (raw)
In-Reply-To: <20080902151426.98935cd1.akpm@linux-foundation.org>
On Tue, 2 Sep 2008 15:14:26 -0700
Andrew Morton <akpm@linux-foundation.org> wrote:
> 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
...
>
> 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.
Thanks! This is even better and looks like it meets our needs.
prev parent reply other threads:[~2008-09-03 13:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-29 19:22 [PATCH] Provide control over core name even for multithreaded processes La Monte H.P. Yarroll
2008-09-02 22:14 ` Andrew Morton
2008-09-03 13:50 ` La Monte Yarroll [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=20080903095036.0331de10@kartuli \
--to=piggy@laurelnetworks.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@tv-sign.ru \
/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