Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932981AbbHXRLu (ORCPT ); Mon, 24 Aug 2015 13:11:50 -0400 Received: from mail-qk0-f179.google.com ([209.85.220.179]:33238 "EHLO mail-qk0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755138AbbHXRLr (ORCPT ); Mon, 24 Aug 2015 13:11:47 -0400 Date: Mon, 24 Aug 2015 13:11:44 -0400 From: Tejun Heo To: Jan Kara Cc: Dave Chinner , Eryu Guan , Jens Axboe , linux-kernel@vger.kernel.org, xfs@oss.sgi.com, axboe@fb.com, Jan Kara , linux-fsdevel@vger.kernel.org, kernel-team@fb.com Subject: Re: [PATCH block/for-linus] writeback: fix syncing of I_DIRTY_TIME inodes Message-ID: <20150824171144.GB27262@mtj.duckdns.org> References: <20150818195439.GB15739@mtj.duckdns.org> <20150818215611.GD3902@dastard> <20150821102053.GL17933@dhcp-13-216.nay.redhat.com> <20150822003025.GS3902@dastard> <20150822044609.GM17933@dhcp-13-216.nay.redhat.com> <20150824011123.GA714@dastard> <20150824031816.GO17933@dhcp-13-216.nay.redhat.com> <20150824062425.GU3902@dastard> <20150824091959.GA2936@quack.suse.cz> <20150824145150.GA10029@mtj.duckdns.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150824145150.GA10029@mtj.duckdns.org> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1103 Lines: 27 Hello, On Mon, Aug 24, 2015 at 10:51:50AM -0400, Tejun Heo wrote: > > Bah, I see the problem and indeed it was introduced by commit e79729123f639 > > "writeback: don't issue wb_writeback_work if clean". The problem is that > > we bail out of sync_inodes_sb() if there is no dirty IO. Which is wrong > > because we have to wait for any outstanding IO (i.e. call wait_sb_inodes()) > > regardless of dirty state! And that also explains why Tejun's patch fixes > > the problem because it backs out the change to the exit condition in > > sync_inodes_sb(). > > Dang, I'm an idiot sandwich. A question tho, so this means that an inode may contain dirty or writeback pages w/o the inode being on one of the dirty lists. Looking at the generic filesystem and writeback code, this doesn't seem true in general. Is this something xfs specific? Thanks. -- tejun -- 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/