* [PATCH 2/2] ext4: fix ZERO_RANGE test failure in data journalling
@ 2014-05-13 0:10 Namjae Jeon
2014-05-26 16:29 ` Theodore Ts'o
0 siblings, 1 reply; 2+ messages in thread
From: Namjae Jeon @ 2014-05-13 0:10 UTC (permalink / raw)
To: Theodore Ts'o; +Cc: linux-ext4, Lukáš Czerner, Ashish Sangwan
xfstests generic/091 is failing when mounting ext4 with data=journal.
I think that this regression is same problem that occurred prior to collapse
range issue. So ZERO RANGE also need to call ext4_force_commit as
collapse range.
Signed-off-by: Namjae Jeon <namjae.jeon@samsung.com>
Signed-off-by: Ashish Sangwan <a.sangwan@samsung.com>
---
fs/ext4/extents.c | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/fs/ext4/extents.c b/fs/ext4/extents.c
index 1c5e877..02143d6 100644
--- a/fs/ext4/extents.c
+++ b/fs/ext4/extents.c
@@ -4743,6 +4743,15 @@ static long ext4_zero_range(struct file *file, loff_t offset,
mutex_lock(&EXT4_I(inode)->i_write_mutex);
+ /* Call ext4_force_commit to flush all data in case of data=journal. */
+ if (ext4_should_journal_data(inode)) {
+ ret = ext4_force_commit(inode->i_sb);
+ if (ret) {
+ mutex_unlock(&EXT4_I(inode)->i_write_mutex);
+ return ret;
+ }
+ }
+
/*
* Write out all dirty pages to avoid race conditions
* Then release them.
--
1.7.11-rc0
^ permalink raw reply related [flat|nested] 2+ messages in thread
end of thread, other threads:[~2014-05-26 16:29 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-05-13 0:10 [PATCH 2/2] ext4: fix ZERO_RANGE test failure in data journalling Namjae Jeon
2014-05-26 16:29 ` Theodore Ts'o
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).