Jan Kara 81be12c817 jbd2: fix sending of data flush on journal commit ...

In data=ordered mode, it's theoretically possible (however rare) that
an inode is filed to transaction's t_inode_list and a flusher thread
writes all the data and inode is reclaimed before the transaction
starts to commit.  In such a case, we could erroneously omit sending a
flush to file system device when it is different from the journal
device (because data can still be in disk cache only).

Fix the problem by setting a flag in a transaction when some inode is added
to it and then send disk flush in the commit code when the flag is set.

Signed-off-by: Jan Kara <jack@suse.cz>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>

2011-05-24 11:52:40 -04:00

..

checkpoint.c

Merge branch 'next' into upstream-merge

2010-10-27 23:44:47 -04:00

commit.c

jbd2: fix sending of data flush on journal commit

2011-05-24 11:52:40 -04:00

journal.c

jbd2: only print the debugging information for tid wraparound once

2011-05-08 19:37:54 -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: move debug message into debug #ifdef

2010-12-18 13:36:33 -05:00

revoke.c

Fix common misspellings

2011-03-31 11:26:23 -03:00

transaction.c

jbd2: fix sending of data flush on journal commit

2011-05-24 11:52:40 -04:00