On Tue, Nov 25, 2014 at 04:56:15PM +0100, Jan Kara wrote: > Option journal_async_commit breaks gurantees of data=ordered mode as it > sends only a single cache flush after writing a transaction commit > block. Thus even though the transaction including the commit block is > fully stored on persistent storage, file data may still linger in drives > caches and will be lost on power failure. Since all checksums match on > journal recovery, we replay the transaction thus possibly exposing stale > user data. > > To fix this data exposure issue, remove the possibility to use > journal_async_commit in data=ordered mode. > > Signed-off-by: Jan Kara <jack@xxxxxxx> Applied, thanks. - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
