Re: [PATCH 0/6 v2] Introduce FALLOC_FL_ZERO_RANGE flag for fallocate

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Reiser Filesystem Development]     [Ceph FS]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite National Park]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]     [Linux Media]

  Powered by Linux