Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752892Ab0LOLv6 (ORCPT ); Wed, 15 Dec 2010 06:51:58 -0500 Received: from one.firstfloor.org ([213.235.205.2]:44755 "EHLO one.firstfloor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751345Ab0LOLv5 (ORCPT ); Wed, 15 Dec 2010 06:51:57 -0500 Date: Wed, 15 Dec 2010 12:51:54 +0100 From: Andi Kleen To: "Suzuki K. Poulose" Cc: Tejun Heo , Linus Torvalds , linux-kernel@vger.kernel.org, Jeremy Fitzhardinge , Christoph Hellwig , Masami Hiramatsu , Ananth N Mavinakayanahalli , Daisuke HATAYAMA , Andi Kleen , Roland McGrath , Amerigo Wang , KAMEZAWA Hiroyuki , KOSAKI Motohiro , Oleg Nesterov , Andrew Morton Subject: Re: [RFC] [Patch 0/21] Non disruptive application core dump infrastructure Message-ID: <20101215115153.GB22304@basil.fritz.box> References: <20101214152259.67896960@suzukikp> <20101215110446.157bbb25@suzukikp> <4D088C6C.8020800@kernel.org> <20101215165626.715007b5@suzukikp> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20101215165626.715007b5@suzukikp> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 657 Lines: 17 > 1) A process can trigger a core synchronously, upon an event, say a signal > handler and continue from there. gcore would require a fork(), which is not > safe to use from a signal handler. Why is it not safe for a signal? >From the kernel side it should be. glibc may do some funky things on fork, but you could always call the syscall directly. -Andi -- ak@linux.intel.com -- Speaking for myself only. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/