Linux NFS development
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Trond Myklebust <trond.myklebust@primarydata.com>
Cc: linux-nfs@vger.kernel.org, Olga.Kornievskaia@netapp.com
Subject: Re: [PATCH 2/2] NFSv4.1: Ask for no delegation on OPEN if already holding one
Date: Thu, 5 Feb 2015 06:07:01 -0800	[thread overview]
Message-ID: <20150205140701.GA3941@infradead.org> (raw)
In-Reply-To: <1423000784-93180-2-git-send-email-trond.myklebust@primarydata.com>

On Tue, Feb 03, 2015 at 04:59:44PM -0500, Trond Myklebust wrote:
> If we already hold a delegation, there should be no reason for the
> server to issue it to us again. Unfortunately, there appear to be
> servers out there that engage in this practice. While it is often
> harmless to do so, there is one case where this creates a problem
> and that is when the client is in the process of returning that
> delegation.
> This patch uses the NFSv4.1 NFS4_SHARE_WANT_NO_DELEG flag to inform
> the server not to return a delegation in these cases.

Shouldn't this be patch 1 as it's the actual bug fix that might need
backporting?

  parent reply	other threads:[~2015-02-05 14:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-03 21:59 [PATCH 1/2] NFSv4.1: Ask for no delegation on OPEN if using O_DIRECT Trond Myklebust
2015-02-03 21:59 ` [PATCH 2/2] NFSv4.1: Ask for no delegation on OPEN if already holding one Trond Myklebust
2015-02-03 22:47   ` Kornievskaia, Olga
2015-02-04  1:04     ` Trond Myklebust
2015-02-05 14:07   ` Christoph Hellwig [this message]
2015-02-05 14:49     ` Trond Myklebust
2015-02-04  8:16 ` [PATCH 1/2] NFSv4.1: Ask for no delegation on OPEN if using O_DIRECT Christoph Hellwig
2015-02-04 12:32   ` Trond Myklebust
2015-02-05 11:27     ` Christoph Hellwig

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=20150205140701.GA3941@infradead.org \
    --to=hch@infradead.org \
    --cc=Olga.Kornievskaia@netapp.com \
    --cc=linux-nfs@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