Yongqiang Yang 1ba37268cd jbd2: 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: "Theodore Ts'o" <tytso@mit.edu>

2011-12-28 17:46:46 -05:00

..

checkpoint.c

jbd2: use WRITE_SYNC in journal checkpoint

2011-06-27 12:36:29 -04:00

commit.c

jbd2: clear revoked flag on buffers before a new transaction started

2011-12-28 17:46:46 -05:00

journal.c

jbd2: Unify log messages in jbd2 code

2011-11-01 19:09:18 -04:00

Kconfig

Revert "task_struct: make journal_info conditional"

2009-12-17 13:23:24 -08:00

Makefile

[PATCH] jbd2: rename jbd2 symbols to avoid duplication of jbd symbols

2006-10-11 11:14:15 -07:00

recovery.c

jbd2: Unify log messages in jbd2 code

2011-11-01 19:09:18 -04:00

revoke.c

jbd2: clear revoked flag on buffers before a new transaction started

2011-12-28 17:46:46 -05:00

transaction.c

jbd2: Unify log messages in jbd2 code

2011-11-01 19:09:18 -04:00