From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: qemu-kvm hangs if multipath device is queing Date: Wed, 19 May 2010 09:29:02 +0200 Message-ID: <20100519072902.GA711@lst.de> References: <4BDF3F94.1080608@dlh.net> <4BDFDC44.9030808@redhat.com> <4BE00750.6040804@dlh.net> <4BE01120.30608@redhat.com> <4BE02440.6010802@dlh.net> <4BE028BF.1000603@redhat.com> <4BEAB4B0.70803@dlh.net> <4BED1740.1080604@redhat.com> <4BF275B1.8030106@dlh.net> <4BF2949C.8010108@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Peter Lieven , qemu-devel@nongnu.org, kvm@vger.kernel.org, Christoph Hellwig To: Kevin Wolf Return-path: Received: from verein.lst.de ([213.95.11.210]:52773 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752580Ab0ESH3Z (ORCPT ); Wed, 19 May 2010 03:29:25 -0400 Content-Disposition: inline In-Reply-To: <4BF2949C.8010108@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On Tue, May 18, 2010 at 03:22:36PM +0200, Kevin Wolf wrote: > I think it's stuck here in an endless loop: > > while (laiocb->ret == -EINPROGRESS) > qemu_laio_completion_cb(laiocb->ctx); > > Can you verify this by single-stepping one or two loop iterations? ret > and errno after the read call could be interesting, too. Maybe the compiler is just too smart. Without some form of barrier it could just optimize the loop away as laiocb->ret couldn't change in a normal single-threaded environment.