[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.00.1403181006240.24748@localhost.localdomain>
Date: Tue, 18 Mar 2014 10:06:32 +0100 (CET)
From: Lukáš Czerner <lczerner@...hat.com>
To: tytso@....edu
cc: Lukáš Czerner <lczerner@...hat.com>@thunk.org,
linux-ext4@...r.kernel.org
Subject: Re: [PATCH 0/6 v2] Introduce FALLOC_FL_ZERO_RANGE flag for
fallocate
On Mon, 17 Mar 2014, tytso@....edu wrote:
> Date: Mon, 17 Mar 2014 17:00:30 -0400
> From: tytso@....edu
> To: =?utf-8?B?THVrw6HFoSBDemVybmVyIDxsY3plcm5lckByZWRoYXQuY29tPg==?=@...nk.org
> Cc: linux-ext4@...r.kernel.org
> Subject: Re: [PATCH 0/6 v2] Introduce FALLOC_FL_ZERO_RANGE flag for fallocate
>
> On Mon, Mar 17, 2014 at 01:59:35PM +0100, Lukáš Czerner wrote:
> > > The "dev2" branch in the ext4 git tree has all the patches in this
> > > series (1, 2, and 5) --- 3 was included earlier applied on top of the
> > > "dev" branch. The "test" branch is the dev2 branch with the
> > > xfs-collapse-range branch pulled in, which actually enables the
> > > ZERO_RANGE flags (as well as the collapse range patches).
> > >
> > > When I tried testing with the "test" branch, things failed pretty
> > > quickly. I've attached two of these in this patch set. I'm guessing
> > > it's some kind of memory corruption problem. These failures are
> > > pretty repeatable, and it fails fast.
>
> Can you let me know when you've had a chance to take a look at this
> failure? Once we put back the EOFBLOCK_FL code, I suspect we should
> be fine with the first two patches in this patch series, but patch #5
> plus the xfs-collapse-range branch appears to still have issues.
>
> Thanks!!
>
> - Ted
Yes, I am looking into this since yesterday, but unfortunately I
have not found a problem yet. I am still trying to figure it out.
-Lukas
Powered by blists - more mailing lists