linux-ext4 - Re: Commit Interval and Delayed Allocation

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

Message-ID: <20121110025838.GA5974@thunk.org>
Date:	Fri, 9 Nov 2012 21:58:38 -0500
From:	Theodore Ts'o <tytso@....edu>
To:	"Nelson, John R" <John_Nelson@...dent.uml.edu>
Cc:	"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>
Subject: Re: Commit Interval and Delayed Allocation

On Sat, Nov 10, 2012 at 12:40:42AM +0000, Nelson, John R wrote:
> Hi,
>   Say if ext4 commits every 5 seconds, does this mean whatever is
>buffered for delayed allocation is flushed every 5 seconds as well?

No; there is a separate 30 second timer which is used for writeback
thread.

For ext3 in data=ordered mode, we will flush out dirty pages for
inodes which have been written to make sure that stale data can never
get revealed.

But in delayed allocation, there is no risk that stale data can get
revealed until we actually allocate the data blocks.

	       	  	   	    	- 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