From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752994Ab2GPJ7p (ORCPT ); Mon, 16 Jul 2012 05:59:45 -0400 Received: from www.linutronix.de ([62.245.132.108]:52278 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751123Ab2GPJ7k (ORCPT ); Mon, 16 Jul 2012 05:59:40 -0400 Date: Mon, 16 Jul 2012 11:59:32 +0200 (CEST) From: Thomas Gleixner To: Mike Galbraith cc: Jan Kara , Jeff Moyer , LKML , linux-fsdevel@vger.kernel.org, Tejun Heo , Jens Axboe , mgalbraith@suse.com Subject: Re: Deadlocks due to per-process plugging In-Reply-To: <1342432094.7659.39.camel@marge.simpson.net> Message-ID: References: <20120711133735.GA8122@quack.suse.cz> <20120711201601.GB9779@quack.suse.cz> <20120713123318.GB20361@quack.suse.cz> <20120713144622.GB28715@quack.suse.cz> <1342343673.28142.2.camel@marge.simpson.net> <1342405366.7659.35.camel@marge.simpson.net> <1342432094.7659.39.camel@marge.simpson.net> User-Agent: Alpine 2.02 (LFD 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 16 Jul 2012, Mike Galbraith wrote: > On Mon, 2012-07-16 at 10:59 +0200, Thomas Gleixner wrote: > > On Mon, 16 Jul 2012, Mike Galbraith wrote: > > > On Sun, 2012-07-15 at 11:14 +0200, Mike Galbraith wrote: > > > > On Sun, 2012-07-15 at 10:59 +0200, Thomas Gleixner wrote: > > > > > > > > Can you figure out on which lock the stuck thread which did not unplug > > > > > due to tsk_is_pi_blocked was blocked? > > > > > > > > I'll take a peek. > > > > > > Sorry for late reply, took a half day away from box. Jan had already > > > done the full ext3 IO deadlock analysis: > > > > > > Again kjournald is waiting for buffer IO on block 4367635 (sector > > > 78364838) to finish. Now it is dbench thread 0xffff88026f330e70 which > > > has submitted this buffer for IO and is still holding this buffer behind > > > its plug (request for sector 78364822..78364846). The dbench thread is > > > waiting on j_checkpoint mutex (apparently it has successfully got the > > > mutex in the past, checkpointed some buffers, released the mutex and > > > hung when trying to acquire it again in the next loop of > > > __log_wait_for_space()). > > > > And what's holding j_checkpoint mutex and not making progress? > > Waiting for wakeup from kjournald. So kicking the io in __log_wait_for_space() spin_unlock(&journal->j_state_lock); --> HERE mutex_lock(&journal->j_checkpoint_mutex); should fix the issue, right ? Thanks, tglx