From: Nick Bowler <nbowler@elliptictech.com>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: Chuck Lever <chuck.lever@oracle.com>,
LKML Kernel <linux-kernel@vger.kernel.org>,
"J. Bruce Fields" <bfields@redhat.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: Regression, bisected: sqlite locking failure on nfs
Date: Tue, 2 Nov 2010 10:05:33 -0400 [thread overview]
Message-ID: <20101102140533.GA3695@elliptictech.com> (raw)
In-Reply-To: <1288703671.2925.1.camel@heimdal.trondhjem.org>
On 2010-11-02 09:14 -0400, Trond Myklebust wrote:
> OK. Can you please try the following? It only differs from the last one
> by a small bugfix, and a WARN_ON() in order to try to catch other
> occurrences of the same bug.
[...]
> NLM: Fix a regression in lockd
Things seem to be working fine now, thanks.
Tested-by: Nick Bowler <nbowler@elliptictech.com>
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
next prev parent reply other threads:[~2010-11-02 14:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-01 17:58 Regression, bisected: sqlite locking failure on nfs Nick Bowler
2010-11-01 18:07 ` Chuck Lever
2010-11-01 18:19 ` Nick Bowler
2010-11-01 18:30 ` Chuck Lever
2010-11-01 19:22 ` Trond Myklebust
2010-11-01 19:42 ` Trond Myklebust
2010-11-01 19:45 ` Chuck Lever
2010-11-01 19:48 ` Trond Myklebust
2010-11-01 19:55 ` Chuck Lever
2010-11-01 20:35 ` Trond Myklebust
2010-11-01 21:12 ` Chuck Lever
2010-11-01 20:09 ` Trond Myklebust
2010-11-01 20:33 ` Nick Bowler
2010-11-02 13:14 ` Trond Myklebust
2010-11-02 14:05 ` Nick Bowler [this message]
[not found] ` <1288640536.5009.18.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2010-11-01 19:59 ` Nick Bowler
2010-11-01 19:59 ` Nick Bowler
2010-11-01 19:43 ` Chuck Lever
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=20101102140533.GA3695@elliptictech.com \
--to=nbowler@elliptictech.com \
--cc=Trond.Myklebust@netapp.com \
--cc=bfields@redhat.com \
--cc=chuck.lever@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.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 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.