From: Martin Bligh <mbligh@mbligh.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linus Torvalds <torvalds@osdl.org>, Andi Kleen <ak@suse.de>,
Ingo Molnar <mingo@elte.hu>, Albert Cahalan <acahalan@gmail.com>,
arjan@infradead.org, akpm@osdl.org, linux-kernel@vger.kernel.org,
Roland McGrath <roland@redhat.com>
Subject: Re: utrace vs. ptrace
Date: Tue, 25 Jul 2006 17:20:37 -0700 [thread overview]
Message-ID: <44C6B555.7000300@mbligh.org> (raw)
In-Reply-To: <1153853342.4725.21.camel@localhost>
Alan Cox wrote:
> On Iau, 2006-07-13 at 12:05 -0700, Linus Torvalds wrote:
>
>>Doing core-dumping in user space would be insane. It doesn't give _any_
>>advantages, only disadvantages.
>
>
> It has a number of very real advantages in certain circumstances and the
> only interface the kernel needs to provide is the debugger interface and
> something to "kick" the debugger and reparent to it, or for that matter
> it might even be viable just to pass the helper the fd of an anonymous
> file holding the dump.
>
> Taking out the kernel core dump support would be insane.
>
> We get customers who like to collect/process/do clever stuff with core
> dumps and failure cases. We also get people who want to dump a core that
> excludes the 14GB shared mmap of the database file as another example
> where it helps.
The in-kernel core dumper also seems to hold locks that wedge access
to /proc for that pid, which causes anything walking /proc to wedge.
For large core dumps, that takes far too long, and causes us real
problems
M.
next prev parent reply other threads:[~2006-07-26 0:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-13 5:43 [patch] let CONFIG_SECCOMP default to n Albert Cahalan
2006-07-13 7:04 ` utrace vs. ptrace Ingo Molnar
2006-07-13 9:24 ` Ingo Molnar
2006-07-13 12:37 ` Andi Kleen
2006-07-13 12:43 ` Ingo Molnar
2006-07-13 13:21 ` Andi Kleen
2006-07-13 13:28 ` Arjan van de Ven
2006-07-13 13:34 ` Andi Kleen
2006-07-13 13:37 ` Arjan van de Ven
2006-07-13 13:46 ` Andi Kleen
2006-07-13 19:05 ` Linus Torvalds
2006-07-13 19:47 ` Ingo Molnar
2006-07-14 10:42 ` Paul Jackson
2006-07-25 18:49 ` Alan Cox
2006-07-25 18:27 ` Linus Torvalds
2006-07-25 18:57 ` Olaf Hering
2006-07-25 19:12 ` Ingo Molnar
2006-07-26 0:20 ` Martin Bligh [this message]
2006-07-13 7:07 ` [patch] let CONFIG_SECCOMP default to n andrea
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=44C6B555.7000300@mbligh.org \
--to=mbligh@mbligh.org \
--cc=acahalan@gmail.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=roland@redhat.com \
--cc=torvalds@osdl.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