From: Nix <nix@esperi.org.uk>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.34 nfs fsync() deadlock
Date: Mon, 31 May 2010 19:11:49 +0100 [thread overview]
Message-ID: <87zkzghrfe.fsf@spindle.srvr.nix> (raw)
In-Reply-To: <1275320467.5038.9.camel@heimdal.trondhjem.org> (Trond Myklebust's message of "Mon, 31 May 2010 11:41:07 -0400")
On 31 May 2010, Trond Myklebust said:
> Can you see if the following 2 attached patches (already sent to
> stable@kernel.org) suffice to fix the hang?
It's hard to be absolutely certain (it only fails about a tenth of the
time with this testcase), but it seems to fix it (I've run a hundred or
so tests and it's still going).
prev parent reply other threads:[~2010-05-31 18:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-31 14:41 2.6.34 nfs fsync() deadlock Nix
2010-05-31 15:41 ` Trond Myklebust
2010-05-31 17:14 ` Nix
2010-05-31 18:11 ` Nix [this message]
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=87zkzghrfe.fsf@spindle.srvr.nix \
--to=nix@esperi.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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