Jan Kara fd2cbd4dfa jbd: Write journal superblock with WRITE_FUA after checkpointing ... If journal superblock is written only in disk's caches and other transaction starts reusing space of the transaction cleaned from the log, it can happen blocks of a new transaction reach the disk before journal superblock. When power failure happens in such case, subsequent journal replay would still try to replay the old transaction but some of it's blocks may be already overwritten by the new transaction. For this reason we must use WRITE_FUA when updating log tail and we must first write new log tail to disk and update in-memory information only after that. Signed-off-by: Jan Kara <jack@suse.cz>		2012-05-15 23:34:37 +02:00
..
checkpoint.c	jbd: Write journal superblock with WRITE_FUA after checkpointing	2012-05-15 23:34:37 +02:00
commit.c	jbd: Write journal superblock with WRITE_FUA after checkpointing	2012-05-15 23:34:37 +02:00
journal.c	jbd: Write journal superblock with WRITE_FUA after checkpointing	2012-05-15 23:34:37 +02:00
Kconfig	Revert "task_struct: make journal_info conditional"	2009-12-17 13:23:24 -08:00
Makefile
recovery.c	jbd: Issue cache flush after checkpointing	2012-01-11 13:36:57 +01:00
revoke.c	jbd: clear revoked flag on buffers before a new transaction started	2011-11-22 01:20:53 +01:00
transaction.c	jbd: Refine commit writeout logic	2012-04-11 11:12:44 +02:00