linux-ext4 - Re: write/write/fallocate quota leakage

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: <87ljavtbjp.fsf@linux.vnet.ibm.com>
Date:	Fri, 04 Jun 2010 14:33:06 +0530
From:	"Aneesh Kumar K. V" <aneesh.kumar@...ux.vnet.ibm.com>
To:	Dmitry Monakhov <dmonakhov@...nvz.org>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: write/write/fallocate quota leakage

On Thu, 03 Jun 2010 12:21:01 +0400, Dmitry Monakhov <dmonakhov@...nvz.org> wrote:
> Recently one "write vs fallocate" quota leakage was fixed, but
> not completely. It is still possible if uninitialized extent which
> covers several delay allocated regions converted to initialized one.
> 
> Take a look at test-case attached.
> The issue is clear enough, but I don't have a good solution for now.
> Off course we can add one more restriction to zeroout logic, but this is
> unproductive way because we have to keep zeroout logic simple as possible.
> 
> Aneesh, do you have any sound ideas?
> 

I will have to look at this more closer. Will get back to you.

-aneesh
--
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