Date: Sat, 12 Mar 2005 02:41:14 -0800
From: Andrew Morton <akpm@osdl.org>
To: Junfeng Yang <yjf@stanford.edu>
Cc: chaffee@bmrc.berkeley.edu, mc@cs.Stanford.EDU,
       linux-kernel@vger.kernel.org,
       OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Subject: Re: [CHECKER] crash + fsck cause file systems to contain loops
 (msdos and vfat, 2.6.11)
Message-Id: <20050312024114.173114fb.akpm@osdl.org>
In-Reply-To: <Pine.GSO.4.44.0503120220190.10643-100000@elaine24.Stanford.EDU>
References: <Pine.GSO.4.44.0503120220190.10643-100000@elaine24.Stanford.EDU>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1038
Lines: 26

Junfeng Yang <yjf@stanford.edu> wrote:
>
> We are from the Stanford Checker team and are currently developing a file
>  system checker call FiSC.  FiSC mainly focuses on finding crash-recovery
>  errors.  We applied it to FiSC and found a serious error where crash then
>  recovery cause the file system to contain loops.
> 
>  To reproduce the warning, download and run our test cases at
> 
>  http://fisc.stanford.edu/bug7/crash.c (for msdos)
>  http://fisc.stanford.edu/bug10/crash.c (for vfat)
> 
>  you can also find the crashed disk images in the corresponding
>  directories.
> 
>  We are not sure if these are bugs or not.  Your
>  confirmations/clarifications on this are well appreciated.

Linus's current tree includes support for `mount -o sync' on the msdos and
vfat filesystems.

-
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/