Yongqiang Yang 8c111b3f56 jbd: clear revoked flag on buffers before a new transaction started ... Currently, we clear revoked flag only when a block is reused. However, this can tigger a false journal error. Consider a situation when a block is used as a meta block and is deleted(revoked) in ordered mode, then the block is allocated as a data block to a file. At this moment, user changes the file's journal mode from ordered to journaled and truncates the file. The block will be considered re-revoked by journal because it has revoked flag still pending from the last transaction and an assertion triggers. We fix the problem by keeping the revoked status more uptodate - we clear revoked flag when switching revoke tables to reflect there is no revoked buffers in current transaction any more. Signed-off-by: Yongqiang Yang <xiaoqiangnk@gmail.com> Signed-off-by: Jan Kara <jack@suse.cz>		2011-11-22 01:20:53 +01:00
..
checkpoint.c	jbd: Use WRITE_SYNC in journal checkpoint.	2011-06-28 00:06:41 +02:00
commit.c	jbd: clear revoked flag on buffers before a new transaction started	2011-11-22 01:20:53 +01:00
journal.c	jbd/jbd2: validate sb->s_first in journal_get_superblock()	2011-11-01 19:04:59 -04:00
Kconfig	Revert "task_struct: make journal_info conditional"	2009-12-17 13:23:24 -08:00
Makefile
recovery.c	jbd: Move debug message into #ifdef area	2010-10-28 01:30:01 +02: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: Fix oops in journal_remove_journal_head()	2011-06-27 11:44:37 +02:00