Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751256AbbGaW1h (ORCPT ); Fri, 31 Jul 2015 18:27:37 -0400 Received: from mail.lang.hm ([64.81.33.126]:50335 "EHLO bifrost.lang.hm" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750744AbbGaW1g (ORCPT ); Fri, 31 Jul 2015 18:27:36 -0400 Date: Fri, 31 Jul 2015 15:27:12 -0700 (PDT) From: David Lang X-X-Sender: dlang@asgard.lang.hm To: Daniel Phillips cc: Rik van Riel , Jan Kara , tux3@tux3.org, Linux Kernel Mailing List , linux-fsdevel@vger.kernel.org, OGAWA Hirofumi Subject: Re: [FYI] tux3: Core changes In-Reply-To: Message-ID: References: <67294911-1776-46b8-916d-0e5642a38725@phunq.net> <20150526070910.GA3307@quack.suse.cz> <20150526090058.GA8024@quack.suse.cz> <5564D60E.6000306@phunq.net> <20150527084138.GD2590@quack.suse.cz> <87a8vtdqfz.fsf@mail.parknet.co.jp> <20150623161247.GP2427@quack.suse.cz> <87k2ueepd6.fsf@mail.parknet.co.jp> <20150709160528.GK2900@quack.suse.cz> <874mklaqbn.fsf@mail.parknet.co.jp> <1981a91e-30a9-43ce-9a05-14aa777e46a5@phunq.net> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1621 Lines: 36 On Fri, 31 Jul 2015, Daniel Phillips wrote: > On Friday, July 31, 2015 11:29:51 AM PDT, David Lang wrote: >> We, the Linux Community have less tolerance for losing people's data and >> preventing them from operating than we used to when it was all tinkerer's >> personal data and secondary systems. >> >> So rather than pushing optimizations out to everyone and seeing what >> breaks, we now do more testing and checking for failures before pushing >> things out. > > By the way, I am curious about whose data you think will get lost > as a result of pushing out Tux3 with a possible theoretical bug > in a wildly improbable scenario that has not actually been > described with sufficient specificity to falsify, let alone > demonstrated. you weren't asking about any particular feature of Tux, you were asking if we were still willing to push out stuff that breaks for users and fix it later. Especially for filesystems that can loose the data of whoever is using it, the answer seems to be a clear no. there may be bugs in what's pushed out that we don't know about. But we don't push out potential data corruption bugs that we do know about (or think we do) so if you think this should be pushed out with this known corner case that's not handled properly, you have to convince people that it's _so_ improbable that they shouldn't care about it. David Lang -- 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/