From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [2.6.36-rc1] unmount livelock due to racing with bdi-flusher threads Date: Thu, 30 Sep 2010 22:59:16 -0400 Message-ID: <20101001025916.GA12345@infradead.org> References: <20100821084126.GE31488@dastard> <20100913024128.GC411@dastard> <20100930210250.GE3573@quack.suse.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Dave Chinner , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org To: Jan Kara Return-path: Content-Disposition: inline In-Reply-To: <20100930210250.GE3573@quack.suse.cz> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Thu, Sep 30, 2010 at 11:02:51PM +0200, Jan Kara wrote: > I think the best resolution of this problem would be to change the work > that is submitted via bdi_start_writeback() (i.e., the work without > superblock = work which needs to do locking) to "target based scheme" like > Christoph wanted already some time ago. I actually have a patch to do this > for background writeback so I will just modify it to apply to a wider range > of writeback as well. Or Christoph, do you already have some patches in > this direction? I've not started any work on it yet.