Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753588AbZFATHR (ORCPT ); Mon, 1 Jun 2009 15:07:17 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751684AbZFATHG (ORCPT ); Mon, 1 Jun 2009 15:07:06 -0400 Received: from earthlight.etchedpixels.co.uk ([81.2.110.250]:39769 "EHLO www.etchedpixels.co.uk" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751331AbZFATHE (ORCPT ); Mon, 1 Jun 2009 15:07:04 -0400 Date: Mon, 1 Jun 2009 20:06:30 +0100 From: Alan Cox To: Andi Kleen Cc: paul@mad-scientist.net, Oleg Nesterov , linux-kernel@vger.kernel.org, stable@kernel.org, Andrew Morton , Andi Kleen , Roland McGrath Subject: Re: [PATCH] coredump: Retry writes where appropriate Message-ID: <20090601200630.6b18bcc1@lxorguk.ukuu.org.uk> In-Reply-To: <20090601190914.GV1065@one.firstfloor.org> References: <1243748019.7369.319.camel@homebase.localnet> <20090531111851.07eb1df3@lxorguk.ukuu.org.uk> <20090601161234.GA10486@redhat.com> <1243877766.8547.38.camel@psmith-ubeta.netezza.com> <20090601184934.1fc54411@lxorguk.ukuu.org.uk> <1243881544.8547.66.camel@psmith-ubeta.netezza.com> <20090601200232.078aacbb@lxorguk.ukuu.org.uk> <20090601190914.GV1065@one.firstfloor.org> X-Mailer: Claws Mail 3.7.0 (GTK+ 2.14.7; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1147 Lines: 27 On Mon, 1 Jun 2009 21:09:14 +0200 Andi Kleen wrote: > On Mon, Jun 01, 2009 at 08:02:32PM +0100, Alan Cox wrote: > > > If a program seems to be unresponsive the user could ^C, without > > > realizing that it was really dumping core. Now when they are asked to > > > produce the core so the problem can be debugged, they can't do it. Or, > > > > and get their prompt back, which is probably why they are banging ^C. If > > they didn't want their prompt back at that point they'd still be > > wondering why nothing was occuring at the point it said (core dumped) > > Maybe we need a background core dump? You can pretty much implement that via the pipe handler if you care. Just buffer aggressively. For the general case however programs assume that when wait() returns indicating the core dump occurred that they can immediately access the dump (eg bug-buddy in Gnome) Alan -- 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/