bdi_writeback_workfn() uses wb_has_dirty_io() to determine whether it should schedule writeback work in future. With per-sb dirty tracking we are going to have more dirty lists for bdi so we have to use bdi_has_dirty_io() which will properly iterate all of the lists. Signed-off-by: Jan Kara <jack@xxxxxxx> --- fs/fs-writeback.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/fs-writeback.c b/fs/fs-writeback.c index 4247e1f7cb03..c8806c81e37c 100644 --- a/fs/fs-writeback.c +++ b/fs/fs-writeback.c @@ -957,7 +957,7 @@ void bdi_writeback_workfn(struct work_struct *work) if (!list_empty(&bdi->work_list)) mod_delayed_work(bdi_wq, &bdi->dwork, 0); - else if (wb_has_dirty_io(wb) && dirty_writeback_interval) + else if (bdi_has_dirty_io(bdi) && dirty_writeback_interval) bdi_wakeup_thread_delayed(bdi); current->flags &= ~PF_SWAPWRITE; -- 1.8.1.4 -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
