From: Jeff Garzik <jeff@garzik.org>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: NFSv4: Give the lock stateid its own sequence queue
Date: Thu, 10 Jan 2008 16:25:31 -0500 [thread overview]
Message-ID: <47868D4B.6030608@garzik.org> (raw)
In-Reply-To: <1199999274.13775.16.camel@heimdal.trondhjem.org>
Trond Myklebust wrote:
> Sharing the open sequence queue causes a deadlock when we try to take both
> a lock sequence id and and open sequence id.
>
> This fixes the regression reported by Dimitri Puzin and Jeff Garzik:
> See http://bugzilla.kernel.org/show_bug.cgi?id=9712
>
> Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
Tested-by: Jeff Garzik <jgarzik@redhat.com>
prev parent reply other threads:[~2008-01-10 21:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-10 21:07 NFSv4: Give the lock stateid its own sequence queue Trond Myklebust
2008-01-10 21:25 ` Jeff Garzik [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=47868D4B.6030608@garzik.org \
--to=jeff@garzik.org \
--cc=Trond.Myklebust@netapp.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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