| To: | Jan Kara <jack@xxxxxxx> |
|---|---|
| Subject: | Re: [PATCH block/for-linus] writeback: fix syncing of I_DIRTY_TIME inodes |
| From: | Tejun Heo <tj@xxxxxxxxxx> |
| Date: | Mon, 24 Aug 2015 13:11:44 -0400 |
| Cc: | Dave Chinner <david@xxxxxxxxxxxxx>, Eryu Guan <eguan@xxxxxxxxxx>, Jens Axboe <axboe@xxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx, axboe@xxxxxx, Jan Kara <jack@xxxxxxxx>, linux-fsdevel@xxxxxxxxxxxxxxx, kernel-team@xxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=vDYTqx49tpzJTIiPzjqo7pFXDc3qIPmfdxBM2UAvcrY=; b=k6qJXeE7u5c1YOE6ZT1j84ip9IdvzAs4f7tKpVF9Qk+sUM3iRlFYJgbnP/hlnHBdKw gFk/adH7ON+y3x9zXMD5hhks99EShMHrXo3h3PvT+a7ryqbDSWX6YH5qxETuT18kcCCE OPX7tbYS7hKRdYImfRHA73B2JONxlErFZQWS1J95FNgsMnkbxcwob2eK95TKZUhIXlNs RSilKgdX1mxrv5MFm5yl5Ti6XlRDZluCD4qAIkr5SnR8ifbXY4QbW8wrsV1ICAfA5U12 ZDGDFY6qEJPQrw/dxp0sZPQoRG9anTVjaMLDmGO65ZWWeDiD4tskY59T/0nE3aER0x9E 4IMg== |
| In-reply-to: | <20150824145150.GA10029@xxxxxxxxxxxxxxx> |
| References: | <20150818195439.GB15739@xxxxxxxxxxxxxxx> <20150818215611.GD3902@dastard> <20150821102053.GL17933@xxxxxxxxxxxxxxxxxxxxxxxxxx> <20150822003025.GS3902@dastard> <20150822044609.GM17933@xxxxxxxxxxxxxxxxxxxxxxxxxx> <20150824011123.GA714@dastard> <20150824031816.GO17933@xxxxxxxxxxxxxxxxxxxxxxxxxx> <20150824062425.GU3902@dastard> <20150824091959.GA2936@xxxxxxxxxxxxx> <20150824145150.GA10029@xxxxxxxxxxxxxxx> |
| Sender: | Tejun Heo <htejun@xxxxxxxxx> |
| User-agent: | Mutt/1.5.23 (2014-03-12) |
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 |
| Previous by Date: | Re: How to determine the reserved blocks in xfs filesystem ?, Emmanuel Florac |
|---|---|
| Next by Date: | Re: [PATCH block/for-linus] writeback: fix syncing of I_DIRTY_TIME inodes, Tejun Heo |
| Previous by Thread: | Re: [PATCH block/for-linus] writeback: fix syncing of I_DIRTY_TIME inodes, Tejun Heo |
| Next by Thread: | Re: [PATCH block/for-linus] writeback: fix syncing of I_DIRTY_TIME inodes, Jan Kara |
| Indexes: | [Date] [Thread] [Top] [All Lists] |