From mboxrd@z Thu Jan 1 00:00:00 1970 From: Theodore Tso Subject: Re: Fix(es) for ext2 fsync bug Date: Thu, 15 Feb 2007 20:18:27 -0500 Message-ID: <20070216011827.GG5285@thunk.org> References: <20070215185412.455311810F7D0@csl.stanford.edu> <21e789ec0702151118x1c6af801gd34981d72db0f5b2@mail.gmail.com> <21e789ec0702151128x744f61e5lb24d2da972af185a@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: engler@csl.stanford.edu, sfaibish , Dave Kleikamp , Valerie Henson , linux-fsdevel@vger.kernel.org, Can Sar To: Junfeng Yang Return-path: Received: from thunk.org ([69.25.196.29]:55486 "EHLO thunker.thunk.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751851AbXBPBSr (ORCPT ); Thu, 15 Feb 2007 20:18:47 -0500 Content-Disposition: inline In-Reply-To: <21e789ec0702151128x744f61e5lb24d2da972af185a@mail.gmail.com> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Thu, Feb 15, 2007 at 11:28:46AM -0800, Junfeng Yang wrote: > > Actually, we found a crash-during-recovery bug in ext3 too. It's a race > between resetting the journal super block and replay of the journal. This > bug was fixed by Ted long time ago (3 years?). That was found in your original work (using UML) not the more recent work using EXPLODE, correct? - Ted