linux-kernel - Re: [BUG] copy file result with zero

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] [day] [month] [year] [list]

Message-ID: <alpine.LFD.2.00.1110031751010.4447@dhcp-27-109.brq.redhat.com>
Date:	Mon, 3 Oct 2011 17:51:57 +0200 (CEST)
From:	Lukas Czerner <lczerner@...hat.com>
To:	"Ted Ts'o" <tytso@....edu>
cc:	Lukas Czerner <lczerner@...hat.com>,
	Yongqiang Yang <xiaoqiangnk@...il.com>,
	Andreas Dilger <aedilger@...il.com>,
	Jeff liu <jeff.liu@...cle.com>,
	Dave Young <hidave.darkstar@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-ext4@...r.kernel.org
Subject: Re: [BUG] copy file result with zero

On Mon, 3 Oct 2011, Ted Ts'o wrote:

> On Mon, Oct 03, 2011 at 03:11:30PM +0200, Lukas Czerner wrote:
> > 
> > Oops, you're right. I think that the best solution would be to revert
> > the commit
> > 
> > c03f8aa9abdd517477c2021ea1251939b4da49e6
> > ext4: use FIEMAP_EXTENT_LAST flag for last extent in fiemap
> > 
> > and then fix the original problem with your delayed extent tree
> > solution, where we can easily check not only for next allocated extent,
> > but also for next delayed extent to see if the current one is last or
> > not.
> > ...
> >
> > I do not know how "ready" are your patches..Is it possible to wait for
> > them to be ready and fix it in your patch set ? That means, revert the
> > mentioned commit and reimplement fiemap with delayed extent tree.
> 
> Sigh, yeah, we need to fix this to avoid the hang in xfstests #252 but
> users losing data even if the coreutils release was only out there for
> 13 days is bad juju.
> 
> I'm working on reviewing the kernel patch backlog this week, and I'll
> give this series one priority.

Actually the series needs to be changed to to fix the problem. I'll
comment the appropriate patch.

Thanks!
-Lukas
> 
> Thanks to Yongqiang and Lukas for looking into this!
> 
> 							- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/