From: Christoph Hellwig <hch@lst.de>
To: bfields@redhat.com
Cc: linux-nfs@vger.kernel.org
Subject: [pynfs PATCH] check that a mixed size / uid setattr works
Date: Sun, 22 Jan 2017 17:51:18 +0100 [thread overview]
Message-ID: <1485103878-15160-1-git-send-email-hch@lst.de> (raw)
On some Linux file systems this currently fails and/or trips an ASSERT.
Signed-off-by: Christoph Hellwig <hch@lst.de>
---
nfs4.0/servertests/st_setattr.py | 29 +++++++++++++++++++++++++++++
1 file changed, 29 insertions(+)
diff --git a/nfs4.0/servertests/st_setattr.py b/nfs4.0/servertests/st_setattr.py
index b6a398b..accd807 100644
--- a/nfs4.0/servertests/st_setattr.py
+++ b/nfs4.0/servertests/st_setattr.py
@@ -27,6 +27,23 @@ def _set_size(t, c, file, stateid=None, msg=" using stateid=0"):
check(res, msg="Changing size from %i to 0" % newsize)
check_res(t, c, res, file, dict)
+#
+# Mix size and non-size attributes in a single SETATTR. Some Linux file
+# systems aren't happy with this mix, and a server passing this on 1:1
+# will trigger warnings or incorrect results.
+#
+def _set_mixed(t, c, file, stateid=None, msg=" using stateid=0"):
+ startsize = c.do_getattr(FATTR4_SIZE, file)
+ newsize = startsize + 10
+ owner = "65534" # nobody
+
+ dict = {FATTR4_SIZE: newsize, FATTR4_OWNER: owner}
+ ops = c.use_obj(file) + [c.setattr(dict, stateid)]
+ res = c.compound(ops)
+ check(res, msg="Changing size from %i to %i and owner to %s%s" %
+ (startsize, newsize, owner, msg), warnlist=[NFS4ERR_BAD_STATEID])
+ check_res(t, c, res, file, dict)
+
def _try_readonly(t, env, path):
c = env.c1
baseops = c.use_obj(path)
@@ -701,3 +718,15 @@ def testChangeGranularity(t, env):
chattr4 = res.resarray[7].obj_attributes
if chattr1 == chattr2 or chattr2 == chattr3 or chattr3 == chattr4:
t.fail("consecutive SETATTR(mode)'s don't all change change attribute")
+
+def testMixed(t, env):
+ """SETATTR(FATTR4_SIZE + FATTR4_OWNER) on file with stateid = 0
+
+ FLAGS: setattr file all
+ DEPEND: MKFILE
+ CODE: SATT16
+ """
+ c = env.c1
+ c.init_connection()
+ fh, stateid = c.create_confirm(t.code, deny=OPEN4_SHARE_DENY_NONE)
+ _set_mixed(t, c, fh)
--
2.1.4
next reply other threads:[~2017-01-22 16:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-22 16:51 Christoph Hellwig [this message]
2017-01-23 16:52 ` [pynfs PATCH] check that a mixed size / uid setattr works 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=1485103878-15160-1-git-send-email-hch@lst.de \
--to=hch@lst.de \
--cc=bfields@redhat.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).