linux-ext4 - Re: [PATCH] ext4: Fix data corruption when writing to prealloc area

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1216407820.8232.1.camel@mingming-laptop>
Date:	Fri, 18 Jul 2008 12:03:40 -0700
From:	Mingming Cao <cmm@...ibm.com>
To:	"Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>
Cc:	tytso@....edu, sandeen@...hat.com, linux-ext4@...r.kernel.org,
	Shehjar Tikoo <shehjart@....unsw.edu.au>
Subject: Re: [PATCH] ext4: Fix data corruption when writing to prealloc area


在 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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html