linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Malahal Naineni <malahal@us.ibm.com>
To: linux-nfs@vger.kernel.org, Trond.Myklebust@netapp.com
Subject: corruption due to loss of lock
Date: Thu, 13 Jun 2013 13:47:37 -0500	[thread overview]
Message-ID: <20130613184737.GA25713@us.ibm.com> (raw)

Hi Trond,

I saw Bryan's patches here https://patchwork.kernel.org/patch/987402/
that fix issues after loss of a lock.  What is the status on this patch
set? Do they need more work? We have an application that uses range
locks on a file. Two threads from two different clients end up writing
to the same a file due to this bug after a lease expiry from a client.

Regards, Malahal.


             reply	other threads:[~2013-06-13 18:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-13 18:47 Malahal Naineni [this message]
2013-07-11 11:13 ` corruption due to loss of lock Jeff Layton
2013-07-11 14:12   ` Malahal Naineni
2013-07-11 14:19   ` Myklebust, Trond
2013-07-11 14:28     ` Jeff Layton
2013-07-11 14:33       ` Myklebust, Trond
2013-07-11 15:20         ` Jeff Layton
2013-07-11 15:39           ` Malahal Naineni
2013-07-11 16:28           ` Myklebust, Trond

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=20130613184737.GA25713@us.ibm.com \
    --to=malahal@us.ibm.com \
    --cc=Trond.Myklebust@netapp.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).