mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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)
Date: Sat, 12 Mar 2005 02:41:14 -0800	[thread overview]
Message-ID: <20050312024114.173114fb.akpm@osdl.org> (raw)
In-Reply-To: <Pine.GSO.4.44.0503120220190.10643-100000@elaine24.Stanford.EDU>

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.


  reply	other threads:[~2005-03-12 10:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-12 10:29 Junfeng Yang
2005-03-12 10:41 ` Andrew Morton [this message]
2005-03-12 11:21   ` Junfeng Yang
2005-03-12 14:28     ` OGAWA Hirofumi
2005-03-13  5:53       ` Junfeng Yang
2005-03-13 11:52         ` OGAWA Hirofumi
2005-03-13 13:45         ` OGAWA Hirofumi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050312024114.173114fb.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=chaffee@bmrc.berkeley.edu \
    --cc=hirofumi@mail.parknet.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mc@cs.Stanford.EDU \
    --cc=yjf@stanford.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®