All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Malahal Naineni <malahal@us.ibm.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 2/2] Open files with OPEN4_SHARE_DENY_NONE for DELEG5 test
Date: Fri, 11 Jul 2014 18:20:07 -0400	[thread overview]
Message-ID: <20140711222007.GD13656@fieldses.org> (raw)
In-Reply-To: <1403542662-8450-2-git-send-email-malahal@us.ibm.com>

Thanks, applying both.

On Mon, Jun 23, 2014 at 11:57:42AM -0500, Malahal Naineni wrote:
> DELEG5 test, while getting the READ delegation, uses
> OPEN4_SHARE_DENY_WRITE as that is the default.

That's a really dumb default, by the way, we should fix it to default to
DENY_NONE.

--b.

> Pass
> OPEN4_SHARE_DENY_NONE explicitly as that is assumed
> in the test.
> 
> Signed-off-by: Malahal Naineni <malahal@us.ibm.com>
> ---
>  nfs4.0/servertests/st_delegation.py | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/nfs4.0/servertests/st_delegation.py b/nfs4.0/servertests/st_delegation.py
> index 4da3a7a..eaff326 100644
> --- a/nfs4.0/servertests/st_delegation.py
> +++ b/nfs4.0/servertests/st_delegation.py
> @@ -249,6 +249,7 @@ def testManyReaddeleg(t, env, funct=_recall, response=NFS4_OK):
>              
>          # Get a read delegation
>          res = c.open_file(t.code, access=OPEN4_SHARE_ACCESS_READ,
> +                          deny=OPEN4_SHARE_DENY_NONE,
>                            set_recall=True,
>                            recall_funct=funct, recall_return=response)
>          fh, stateid = c.confirm(t.code, res)
> -- 
> 1.8.3.1
> 

      reply	other threads:[~2014-07-11 22:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-23 16:57 [PATCH 1/2] Check for None to avoid python exception Malahal Naineni
2014-06-23 16:57 ` [PATCH 2/2] Open files with OPEN4_SHARE_DENY_NONE for DELEG5 test Malahal Naineni
2014-07-11 22:20   ` J. Bruce Fields [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=20140711222007.GD13656@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=malahal@us.ibm.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 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.