linux-ext4 - Re: [PATCH] ext4: Do not normalize request from fallocate

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: <20130325144408.GA4733@thunk.org>
Date:	Mon, 25 Mar 2013 10:44:08 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	Lukáš Czerner <lczerner@...hat.com>
Cc:	linux-ext4@...r.kernel.org, gharm@...gle.com
Subject: Re: [PATCH] ext4: Do not normalize request from fallocate

One of the things I've been thinking we need to add for some time is a
new field to the allocation_request structure which gives a hint to
mballoc about how much space we will eventually need (i.e., if we are
doing a 1GB fallocate, or if we know that we have 256megs worth of
dirty pages that we intend to write out in ext4_da_writepages, we
should tell mballoc that); this is different from how much space we
can actually use (i.e., 32,767 blocks given that's the maximum size we
can add in an uninitialized extents).  If mballoc knew this, it could
reserve that much space as a per-file preallocation.

That might be the easist way to solve this particular issue.

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