From: Dominique Martinet <dominique.martinet@cea.fr>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
"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: Wed, 9 Dec 2015 07:23:16 +0100 [thread overview]
Message-ID: <20151209062316.GA29917@nautica> (raw)
In-Reply-To: <CALCETrU1GKGXsp4gmnWJXh2Lp=dBp7K--qt1ViUOKyxpVWBtMQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 629 bytes --]
Andy Lutomirski wrote on Tue, Dec 08, 2015:
> Trace attached. I don't see anything wrong, but I also don't know
> what I'm looking for.
Actually doesn't look good, not sure if trace could be missing messages
but it looks like tags get reused...
Quick and dirty parse script (attached output, it doesn't handle TFLUSH
but there are none in his message):
awk '{print NR " " $0}' 9ptrace.txt | \
awk '/^[0-9]* T/ {
if ($5 in tag) {
print "DOUBLETAG " $0 " || had " tag[$5];
} else {
tag[$5] = $0;
}
}
/^[0-9]* R/ {
if (! $5 in tag ) {
print "MISSTAG " $0;
} else {
delete tag[$5];
}
}'
--
Dominique Martinet
[-- Attachment #2: 9pdoubles.xz --]
[-- Type: application/octet-stream, Size: 5524 bytes --]
next prev parent reply other threads:[~2015-12-09 6:23 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
2015-12-08 22:49 ` Andy Lutomirski
2015-12-09 6:23 ` Dominique Martinet [this message]
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=20151209062316.GA29917@nautica \
--to=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 \
--cc=viro@zeniv.linux.org.uk \
/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).