From: "J. Bruce Fields" <bfields@xxxxxxxxxx>
>From 3530 section 8.1.4:
In the case of WRITE-type operations (i.e., WRITEs and SETATTRs
which set size), the server must verify that the access mode
allows writing and return an NFS4ERR_OPENMODE error if it does
not. In the case, of READ, the server may perform the
corresponding check on the access mode, or it may choose to
allow READ on opens for WRITE only, to accommodate clients whose
write implementation may unavoidably do reads (e.g., due to
buffer cache constraints).
Signed-off-by: J. Bruce Fields <bfields@xxxxxxxxxx>
---
nfs4.0/servertests/st_read.py | 14 --------------
1 files changed, 0 insertions(+), 14 deletions(-)
diff --git a/nfs4.0/servertests/st_read.py b/nfs4.0/servertests/st_read.py
index 639b436..cce9a03 100644
--- a/nfs4.0/servertests/st_read.py
+++ b/nfs4.0/servertests/st_read.py
@@ -219,17 +219,3 @@ def testOldStateid(t, env):
fh, stateid = c.confirm(t.code, res)
res = c.read_file(fh, stateid=oldstateid)
check(res, NFS4ERR_OLD_STATEID, "READ with old stateid")
-
-def testOpenMode(t, env):
- """READ with file opened in WRITE mode should return NFS4_OK or NFS4ERR_OPENMODE
-
- FLAGS: read all
- DEPEND: MKFILE
- CODE: RD12
- """
- c = env.c1
- c.init_connection()
- fh, stateid = c.create_confirm(t.code, access=OPEN4_SHARE_ACCESS_WRITE)
- res = c.read_file(fh, stateid=stateid)
- check(res, NFS4ERR_OPENMODE, "READ with file opened in WRITE mode",
- [NFS4_OK])
--
1.7.5.4
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
