Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932591AbbLHCdf (ORCPT ); Mon, 7 Dec 2015 21:33:35 -0500 Received: from zeniv.linux.org.uk ([195.92.253.2]:38105 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932392AbbLHCdd (ORCPT ); Mon, 7 Dec 2015 21:33:33 -0500 Date: Tue, 8 Dec 2015 02:33:31 +0000 From: Al Viro To: Andy Lutomirski Cc: Dominique Martinet , "linux-kernel@vger.kernel.org" , V9FS Developers , Linux FS Devel Subject: Re: [V9fs-developer] Hang triggered by udev coldplug, looks like a race Message-ID: <20151208023331.GJ20997@ZenIV.linux.org.uk> References: <20151207224643.GA10531@nautica> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 948 Lines: 20 On Mon, Dec 07, 2015 at 05:59:41PM -0800, Andy Lutomirski wrote: > If I dump all task states (see attached typescript), I see a bunch of > things blocked in 9p rpc. This makes me think it could be a QEMU bug, > not a kernel bug. Maybe, maybe not - I'd suggest dumping the 9p traffic and checking the request and response IDs; at least one bug in that area got fixed (see commit a84b69 for gory details). Really, check if something gets screwed with IDs. They should be unique among outstanding requests and never reused until either a response with the matching ID arrives, *or* TFLUSH on that ID is sent and reply has arrived. If those rules get buggered, it's very easy to get hangs like that. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/