From: Al Viro <viro@ZenIV.linux.org.uk>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Dominique Martinet <dominique.martinet@cea.fr>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
V9FS Developers <v9fs-developer@lists.sourceforge.net>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>
Subject: Re: [V9fs-developer] Hang triggered by udev coldplug, looks like a race
Date: Tue, 8 Dec 2015 02:33:31 +0000 [thread overview]
Message-ID: <20151208023331.GJ20997@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CALCETrU7SOhTi0g0=tvcirn_C4s9oTkhaV8BfbDf2F90+himJA@mail.gmail.com>
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.
next prev parent reply other threads:[~2015-12-08 2:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-04 5:52 Hang triggered by udev coldplug, looks like a race Andy Lutomirski
2015-12-07 19:18 ` Andy Lutomirski
2015-12-07 22:46 ` [V9fs-developer] " Dominique Martinet
2015-12-08 1:59 ` Andy Lutomirski
2015-12-08 2:33 ` Al Viro [this message]
2015-12-08 22:49 ` Andy Lutomirski
2015-12-09 6:23 ` Dominique Martinet
2015-12-09 6:41 ` Dominique Martinet
2015-12-09 6:45 ` Al Viro
2015-12-17 21:06 ` Andy Lutomirski
2015-12-24 10:51 ` Dominique Martinet
2015-12-30 6:43 ` Andy Lutomirski
2016-01-04 15:59 ` Peter Zijlstra
2016-01-04 16:09 ` Dominique Martinet
2016-01-04 19:07 ` Andy Lutomirski
2016-01-04 19:27 ` Peter Zijlstra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151208023331.GJ20997@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=dominique.martinet@cea.fr \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=v9fs-developer@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).