Prev: Perf trace event parse errors for KVM events
Next: writeback: fix non-integrity write-back
From: Artem Bityutskiy on 26 May 2010 09:20
From: Artem Bityutskiy <Artem.Bityutskiy(a)nokia.com>

This is a fix for commit 7c8a3554. Note, I only compile-tested
this.

Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy(a)nokia.com>
---
fs/fs-writeback.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/fs/fs-writeback.c b/fs/fs-writeback.c
index ea8592b..0242855 100644
--- a/fs/fs-writeback.c
+++ b/fs/fs-writeback.c
@@ -920,7 +920,7 @@ long wb_do_writeback(struct bdi_writeback *wb, int force_wait)
if (force_wait)
work->args.sync_mode = args.sync_mode = WB_SYNC_ALL;

- post_clear = WB_SYNC_ALL || args.sb_pinned;
+ post_clear = args.sync_mode == WB_SYNC_ALL || args.sb_pinned;

/*
* If this isn't a data integrity operation, just notify
--
1.6.6.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: Perf trace event parse errors for KVM events
Next: writeback: fix non-integrity write-back