xfs
[Top] [All Lists]

Re: [PATCH block/for-linus] writeback: fix syncing of I_DIRTY_TIME inode

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, 17 Aug 2015 16:02:54 -0400
Cc: Jens Axboe <axboe@xxxxxxxxx>, Jan Kara <jack@xxxxxxxx>, Eryu Guan <eguan@xxxxxxxxxx>, xfs@xxxxxxxxxxx, axboe@xxxxxx, Dave Chinner <david@xxxxxxxxxxxxx>, linux-fsdevel@xxxxxxxxxxxxxxx, linux-kernel@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=8EAN/gOCokrzNRaZI1j+Fil2vPA1mjo7z1EeQMXnQjk=; b=Io6o/Z7XXxp9OQkUKjsQkU2jlm87fmMTspggL5YxmlsutIKOSn/tfE44YR+MqGcG9q n/2sCrWB9WIoDvmkeIL9fZiNEXy7c2M6heYBButldndJi4W+UXYjHUwIS386KX7h488F FEL9ho5y06OAiMMUPqsY82fP108ZT6jIgXq+ZcCKmRpYMsOsLLazBHQ6V5Wcx080Yuxt OcweXLvod1xxYENBeKAt1QagvtkOhCGlrExoGUxUO8fodbVaxfNI6cORAG10wZeUhnbY gyk8P1leuMQC5tWzzSm5nQwUm9dyBS/tgE08boDHKUQYcLaFcziyp0yGJe16KN/LdSvZ HHIQ==
In-reply-to: <20150814111408.GB8710@xxxxxxxxxxxxx>
References: <20150812101204.GE17933@xxxxxxxxxxxxxxxxxxxxxxxxxx> <20150813004435.GN3902@dastard> <20150813224415.GG4496@xxxxxxxxxxxxxxx> <20150814111408.GB8710@xxxxxxxxxxxxx>
Sender: Tejun Heo <htejun@xxxxxxxxx>
User-agent: Mutt/1.5.23 (2014-03-12)
Hello, Jan.

On Fri, Aug 14, 2015 at 01:14:09PM +0200, Jan Kara wrote:
> So the patch looks good to me. But the fact that is fixes Eryu's problem
> means there is something fishy going on. Either inodes get wrongly attached

Seriously, it shouldn't affect size syncing or xfs but then again my
understanding of xfs is severely limited.

> to b_dirty_time list or bdi_has_dirty_io() somehow misbehaves only
> temporarily and we don't catch it with the debug patch.
> 
> Can we add a test to wb_has_dirty_io() to also check whether it matches
> bdi_has_dirty_io()? Since Eryu doesn't use lazytime (I assume, Eryu, please
> speak up if you do), we could also warn if b_dirty_time lists get
> non-empty. Hmm?

Sure, will prep a patch soon.

Thanks.

-- 
tejun

<Prev in Thread] Current Thread [Next in Thread>