From: Tuomas Tynkkynen <tuomas@tuxera.com>
To: Eric Van Hensbergen <ericvh@gmail.com>
Cc: V9FS Developers <v9fs-developer@lists.sourceforge.net>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 9pfs hangs since 4.7
Date: Fri, 2 Dec 2016 22:11:22 +0200 [thread overview]
Message-ID: <20161202221122.296f130e@duuni> (raw)
In-Reply-To: <CAFkjPTkLVCf363Mi1zc5+5jUNGLtU2t=Xk-YiwMkCmHhAiyn2g@mail.gmail.com>
On Tue, 29 Nov 2016 10:39:39 -0600
Eric Van Hensbergen <ericvh@gmail.com> wrote:
> Any idea of what xfstests is doing at this point in time? I'd be a
> bit worried about some sort of loop in the namespace since it seems to
> be in path traversal. Could also be some sort of resource leak or
> fragmentation, I'll admit that many of the regression tests we do are
> fairly short in duration. Another approach would be to look at doing
> this with a different server (over a network link instead of virtio)
> to isolate it as a client versus server side problem (although from
> the looks of things this does seem to be a client issue).
The xfstests part where it hangs is either of these loops:
FILES=1000
for i in `seq 0 1 $FILES`; do
(
sleep 5
xfs_io -f -c "truncate 10485760" $SCRATCH_MNT/testfile.$i
dd if=/dev/zero of=$SCRATCH_MNT/testfile.$i bs=4k conv=notrunc
) > /dev/null 2>&1 &
done
wait
for i in `seq 0 1 $FILES`; do
dd of=/dev/null if=$SCRATCH_MNT/testfile.$i bs=512k iflag=direct > /dev/null 2>&1 &
done
wait
So all what's happening on the 9p is a bunch of reads+opens
on the binaries (sleep, xfs_io, dd) and their .so dependencies
(which includes some readlinks as well apparently).
I also tried building QEMU with tracing support enabled and
according to its own 9p event log the server did end up replying
to each client request (i.e. each v9fs_foo with a given tag was
was matched up with a v9fs_foo_return or a v9fs_rerror)...
so yes, looking more like a client problem.
next prev parent reply other threads:[~2016-12-02 20:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-24 19:50 9pfs hangs since 4.7 Tuomas Tynkkynen
2016-11-29 16:39 ` Eric Van Hensbergen
2016-12-02 20:11 ` Tuomas Tynkkynen [this message]
2017-01-02 8:20 ` Tuomas Tynkkynen
2017-01-02 16:23 ` Al Viro
2017-01-03 23:34 ` Tuomas Tynkkynen
2017-01-04 1:47 ` Al Viro
2017-01-04 20:04 ` Tuomas Tynkkynen
2017-01-04 23:01 ` Al Viro
2017-01-06 13:52 ` [V9fs-developer] " Greg Kurz
2017-01-07 6:26 ` Al Viro
2017-01-07 15:10 ` Greg Kurz
2017-01-07 17:19 ` Al Viro
2017-01-07 18:15 ` Al Viro
2017-01-08 5:46 ` Al Viro
2017-01-10 8:16 ` Greg Kurz
2017-01-09 18:29 ` Greg Kurz
2017-01-09 18:39 ` Tuomas Tynkkynen
2017-01-09 20:05 ` Al Viro
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=20161202221122.296f130e@duuni \
--to=tuomas@tuxera.com \
--cc=ericvh@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.