From: Christoph Hellwig <hch@infradead.org>
To: Jeff Layton <jeff.layton@primarydata.com>
Cc: netdev@vger.kernel.org, Christoph Hellwig <hch@infradead.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
Bruce Fields <bfields@fieldses.org>,
Trond Myklebust <trond.myklebust@primarydata.com>
Subject: Re: nfs stalls over loopback interface (no sk_data_ready events?)
Date: Thu, 30 Oct 2014 12:00:35 -0700 [thread overview]
Message-ID: <20141030190035.GA23129@infradead.org> (raw)
In-Reply-To: <20141029102123.58f6c960@tlielax.poochiereds.net>
On Wed, Oct 29, 2014 at 10:21:23AM -0400, Jeff Layton wrote:
> Looks some change that went into -rc2 has fixed the problem for me.
> Christoph, can you confirm that this no longer occurs with -rc2?
I can't reproduce it anymore on -rc2.
However:
generic/133 fails fairly reliably with:
Buffered writer, buffered reader
+pread64: Device or resource busy
next prev parent reply other threads:[~2014-10-30 19:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 19:29 nfs stalls over loopback interface (no sk_data_ready events?) Jeff Layton
2014-10-29 14:21 ` Jeff Layton
2014-10-30 19:00 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-10-27 19:26 Jeff Layton
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=20141030190035.GA23129@infradead.org \
--to=hch@infradead.org \
--cc=bfields@fieldses.org \
--cc=jeff.layton@primarydata.com \
--cc=linux-nfs@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=trond.myklebust@primarydata.com \
/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