[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4D088C6C.8020800@kernel.org>
Date: Wed, 15 Dec 2010 10:37:48 +0100
From: Tejun Heo <tj@...nel.org>
To: "Suzuki K. Poulose" <suzuki@...ibm.com>
CC: Linus Torvalds <torvalds@...ux-foundation.org>,
linux-kernel@...r.kernel.org,
Jeremy Fitzhardinge <jeremy.fitzhardinge@...rix.com>,
Christoph Hellwig <hch@....de>,
Masami Hiramatsu <mhiramat@...hat.com>,
Ananth N Mavinakayanahalli <ananth@...ibm.com>,
Daisuke HATAYAMA <d.hatayama@...fujitsu.com>,
Andi Kleen <andi@...stfloor.org>,
Roland McGrath <roland@...hat.com>,
Amerigo Wang <amwang@...hat.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
Oleg Nesterov <oleg@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [RFC] [Patch 0/21] Non disruptive application core dump infrastructure
Hello, Suzuki.
On 12/15/2010 06:34 AM, Suzuki K. Poulose wrote:
> I'd be very glad not using the freezer if there is a neat way to
> accomplish this without the undesired side effects. Tejun's ptrace
> enhancement would still require a userland program to control
> it(gcore); something contained in the kernel would be ideal.
Why is using gcore a bad thing? If we make ptrace avoid the implicit
SIGSTOP, the side effects of ptrace would be the same as using freezer
but with the benefit that it's properly integrated to the process
model and job control.
Thanks.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists