lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  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]
Date:	Sat, 25 Dec 2010 09:39:16 -0500
From:	Ted Ts'o <tytso@....edu>
To:	Yongqiang Yang <xiaoqiangnk@...il.com>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: confused by delayed allocation and ordered journal

On Sat, Dec 25, 2010 at 09:15:28PM +0800, Yongqiang Yang wrote:
> 
> I found that if a block'allocation is delayed, and is not allocated
> when journal flushes it, then journal just redirties it and return in
> journal_submit_data_buffers.
> 
> If I understand right, how to guarantee that the journal mode is ordered?

The primary goal of ordered mode is to make sure that stale data is
not exposed after a crash.  To the extent that delayed allocation also
achieves this goal, it's fine.  The fact that ext3 forced data blocks
out as part of its jbd commit function was always an implementation
detail.

In the long run we'll be getting rid of ordered mode even more so, by
writing the data block first, and only then updating the file system
metadata.  At that point there will be no ordered flushing at all, and
in fact ordered mode will go away as a journal mode supported by ext4.

   		     	     	  - 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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux - Powered by OpenVZ