Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752585AbaBQJVB (ORCPT ); Mon, 17 Feb 2014 04:21:01 -0500 Received: from cantor2.suse.de ([195.135.220.15]:33754 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751592AbaBQJU6 (ORCPT ); Mon, 17 Feb 2014 04:20:58 -0500 Date: Mon, 17 Feb 2014 10:20:54 +0100 From: Jan Kara To: Derek Basehore Cc: Alexander Viro , Jan Kara , Andrew Morton , Tejun Heo , Greg Kroah-Hartman , "Darrick J. Wong" , Kees Cook , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, bleung@chromium.org, sonnyrao@chromium.org, semenzato@chromium.org Subject: Re: [PATCH] backing_dev: Fix hung task on sync Message-ID: <20140217092054.GA3686@quack.suse.cz> References: <1392437537-27392-1-git-send-email-dbasehore@chromium.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1392437537-27392-1-git-send-email-dbasehore@chromium.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri 14-02-14 20:12:17, Derek Basehore wrote: > bdi_wakeup_thread_delayed used the mod_delayed_work function to schedule work > to writeback dirty inodes. The problem with this is that it can delay work that > is scheduled for immediate execution, such as the work from sync_inodes_sb. > This can happen since mod_delayed_work can now steal work from a work_queue. > This fixes the problem by using queue_delayed_work instead. This is a > regression from the move to the bdi workqueue design. > > The reason that this causes a problem is that laptop-mode will change the > delay, dirty_writeback_centisecs, to 60000 (10 minutes) by default. In the case > that bdi_wakeup_thread_delayed races with sync_inodes_sb, sync will be stopped > for 10 minutes and trigger a hung task. Even if dirty_writeback_centisecs is > not long enough to cause a hung task, we still don't want to delay sync for > that long. > > For the same reason, this also changes bdi_writeback_workfn to immediately > queue the work again in the case that the work_list is not empty. The same > problem can happen if the sync work is run on the rescue worker. The patch looks good. You can add: Reviewed-by: Jan Kara I'd also suggest to push this to stable kernels. Honza > > Signed-off-by: Derek Basehore > --- > fs/fs-writeback.c | 5 +++-- > mm/backing-dev.c | 2 +- > 2 files changed, 4 insertions(+), 3 deletions(-) > > diff --git a/fs/fs-writeback.c b/fs/fs-writeback.c > index e0259a1..95b7b8c 100644 > --- a/fs/fs-writeback.c > +++ b/fs/fs-writeback.c > @@ -1047,8 +1047,9 @@ void bdi_writeback_workfn(struct work_struct *work) > trace_writeback_pages_written(pages_written); > } > > - if (!list_empty(&bdi->work_list) || > - (wb_has_dirty_io(wb) && dirty_writeback_interval)) > + if (!list_empty(&bdi->work_list)) > + mod_delayed_work(bdi_wq, &wb->dwork, 0); > + else if (wb_has_dirty_io(wb) && dirty_writeback_interval) > queue_delayed_work(bdi_wq, &wb->dwork, > msecs_to_jiffies(dirty_writeback_interval * 10)); > > diff --git a/mm/backing-dev.c b/mm/backing-dev.c > index ce682f7..3fde024 100644 > --- a/mm/backing-dev.c > +++ b/mm/backing-dev.c > @@ -294,7 +294,7 @@ void bdi_wakeup_thread_delayed(struct backing_dev_info *bdi) > unsigned long timeout; > > timeout = msecs_to_jiffies(dirty_writeback_interval * 10); > - mod_delayed_work(bdi_wq, &bdi->wb.dwork, timeout); > + queue_delayed_work(bdi_wq, &bdi->wb.dwork, timeout); > } > > /* > -- > 1.9.0.rc1.175.g0b1dcb5 > -- Jan Kara SUSE Labs, CR -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/