public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Mingming Cao <cmm@us.ibm.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: tytso@mit.edu, sandeen@redhat.com, linux-ext4@vger.kernel.org,
	Shehjar Tikoo <shehjart@cse.unsw.edu.au>
Subject: Re: [PATCH] ext4: Fix data corruption when writing to prealloc area
Date: Fri, 18 Jul 2008 12:03:40 -0700	[thread overview]
Message-ID: <1216407820.8232.1.camel@mingming-laptop> (raw)
In-Reply-To: <1216401767.6869.19.camel@mingming-laptop>


在 2008-07-18五的 10:22 -0700,Mingming Cao写道:
> 在 2008-07-18五的 10:02 -0700,Mingming Cao写道:
> > I tried this patch, with nodelalloc, the kernel did not crash! Previous
> > it crashes in a few minutes.
> > 
> >  but the test did not stop after fill the file by specified 2G size
> > 
> > 
> > I noticed the write() to write to the last fallocate extent(up to 2G)
> > returns junk value.
> > 
> > 
> > The testcase I got from Shehjart (who originally reported the problem)
> > is  
> > 
> > http://www.gelato.unsw.edu.au/~shehjart/writefallocate.c
> > 
> 
> I forget to mention that I modify the test slight to call fallocate()
> with default mode (expnd size) instead of keep size.
> 

Oh, it's the file size problem for the 2 GB barrier, the latest test
source git tree  has fixed this,.  With the patch ext4 runs fine with
both KEEP_SIZE mode and ALLOCATE mode.

Mingming

--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2008-07-18 19:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-18 13:17 [PATCH] ext4: Fix data corruption when writing to prealloc area Aneesh Kumar K.V
2008-07-18 15:12 ` Eric Sandeen
2008-07-18 16:47   ` Aneesh Kumar K.V
2008-07-18 17:02 ` Mingming Cao
2008-07-18 17:22   ` Mingming Cao
2008-07-18 19:03     ` Mingming Cao [this message]
2008-07-18 20:01 ` Mingming Cao

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=1216407820.8232.1.camel@mingming-laptop \
    --to=cmm@us.ibm.com \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --cc=shehjart@cse.unsw.edu.au \
    --cc=tytso@mit.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