Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757975AbZC1OSf (ORCPT ); Sat, 28 Mar 2009 10:18:35 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755289AbZC1OS1 (ORCPT ); Sat, 28 Mar 2009 10:18:27 -0400 Received: from srv5.dvmed.net ([207.36.208.214]:44369 "EHLO mail.dvmed.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755113AbZC1OS0 (ORCPT ); Sat, 28 Mar 2009 10:18:26 -0400 Message-ID: <49CE3186.8090903@garzik.org> Date: Sat, 28 Mar 2009 10:17:42 -0400 From: Jeff Garzik User-Agent: Thunderbird 2.0.0.21 (X11/20090320) MIME-Version: 1.0 To: Stefan Richter CC: Mark Lord , Linus Torvalds , Matthew Garrett , Alan Cox , Theodore Tso , Andrew Morton , David Rees , Jesper Krogh , Linux Kernel Mailing List Subject: Re: Linux 2.6.29 References: <20090327051338.GP6239@mit.edu> <20090327055750.GA18065@srcf.ucam.org> <20090327062114.GA18290@srcf.ucam.org> <20090327112438.GQ6239@mit.edu> <20090327145156.GB24819@srcf.ucam.org> <20090327150811.09b313f5@lxorguk.ukuu.org.uk> <20090327152221.GA25234@srcf.ucam.org> <20090327161553.31436545@lxorguk.ukuu.org.uk> <20090327162841.GA26860@srcf.ucam.org> <20090327165150.7e69d9e1@lxorguk.ukuu.org.uk> <20090327170208.GA27646@srcf.ucam.org> <49CD2C47.4040300@garzik.org> <49CD4DDF.3000001@garzik.org> <49CD7B10.7010601@garzik.org> <49CD891A.7030103@rtr.ca> <49CD9047.4060500@garzik.org> <49CE2633.2000903@s5r6.in-berlin.de> In-Reply-To: <49CE2633.2000903@s5r6.in-berlin.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -4.4 (----) X-Spam-Report: SpamAssassin version 3.2.5 on srv5.dvmed.net summary: Content analysis details: (-4.4 points, 5.0 required) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 892 Lines: 26 Stefan Richter wrote: > Jeff Garzik wrote: >> Mark Lord wrote: > [store browser session] >>> fsync() isn't going to affect that one way or another >>> unless the entire kernel freezes and dies. >> ...which is one of the three common crash scenarios listed (and >> experienced in the field). > > To get work done which one really cares about, one can always choose a > system which does not crash frequently. Those who run unstable drivers > for thrills surely do it on boxes on which nothing important is being > done, one would think. Once software is perfect, there is definitely a lot of useless crash protection code to remove. Jeff -- 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/