Linux NFS development
 help / color / mirror / Atom feed
From: Malahal Naineni <malahal@us.ibm.com>
To: linux-nfs@vger.kernel.org
Cc: bfields@fieldses.org
Subject: [PATCH 2/2] Open files with OPEN4_SHARE_DENY_NONE for DELEG5 test
Date: Mon, 23 Jun 2014 11:57:42 -0500	[thread overview]
Message-ID: <1403542662-8450-2-git-send-email-malahal@us.ibm.com> (raw)
In-Reply-To: <1403542662-8450-1-git-send-email-malahal@us.ibm.com>

DELEG5 test, while getting the READ delegation, uses
OPEN4_SHARE_DENY_WRITE as that is the default. 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-06-23 16:58 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 ` Malahal Naineni [this message]
2014-07-11 22:20   ` [PATCH 2/2] Open files with OPEN4_SHARE_DENY_NONE for DELEG5 test J. Bruce Fields

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=1403542662-8450-2-git-send-email-malahal@us.ibm.com \
    --to=malahal@us.ibm.com \
    --cc=bfields@fieldses.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox