From: bfields@fieldses.org (J. Bruce Fields)
To: "Su, Yanjun" <suyj.fnst@cn.fujitsu.com>
Cc: "bfields@redhat.com" <bfields@redhat.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"mora@netapp.com" <mora@netapp.com>
Subject: Re: Re: [About] about nfscache problem
Date: Tue, 2 Jun 2020 16:00:14 -0400 [thread overview]
Message-ID: <20200602200014.GD1769@fieldses.org> (raw)
In-Reply-To: <694b44377eae4adca7273de471807be7@G08CNEXMBPEKD05.g08.fujitsu.local>
On Tue, Jun 02, 2020 at 12:50:43AM +0000, Su, Yanjun wrote:
> >On Thu, May 28, 2020 at 07:18:31AM +0000, Su, Yanjun wrote:
> >> This patch adds compatible code for nfsv3 and nfsv4.
>
> >> When we test nfsv4, just use 'chmod' to recall delegation, then
>
> >> run the test. As 'chmod' will modify atime, so use 'noatime' mount option.
>
> >So, you patch nfstest as below, then run the test, and the test fails?
>
> It tests ok when appling the patch.
So you're just asking that this patch be applied to nfstest?
Sorry, I don't think I can help.
--b.
> > Signed-off-by: Su Yanjun <suyj.fnst@xxxxxxxxxxxxxx><mailto:%3Csuyj.fnst@xxxxxxxxxxxxxx%3E>
>
> > ---
>
> > test/nfstest_cache | 12 +++++++++++-
>
> > 1 file changed, 11 insertions(+), 1 deletion(-)
>
> >
>
> > diff --git a/test/nfstest_cache b/test/nfstest_cache
>
> > index 0838418..a31d48f 100755
>
> > --- a/test/nfstest_cache
>
> > +++ b/test/nfstest_cache
>
> > @@ -165,8 +165,13 @@ class CacheTest(TestUtil):
>
> > fd = None
>
> > attr = 'data' if data_cache else 'attribute'
>
> > header = "Verify consistency of %s caching with %s on a file" % (attr,
>
> > self.nfsstr())
>
> > +
>
> > # Mount options
>
> > - mtopts = "hard,intr,rsize=4096,wsize=4096"
>
> > + if self.nfsversion >= 4:
>
> > + mtopts = "noatime,hard,intr,rsize=4096,wsize=4096"
>
> > + else: + mtopts = "hard,intr,rsize=4096,wsize=4096"
>
> > +
>
> > if actimeo:
>
> > header += " actimeo = %d" % actimeo
>
> > mtopts += ",actimeo=%d" % actimeo
>
> > @@ -216,6 +221,11 @@ class CacheTest(TestUtil):
>
> > if fstat.st_size != dlen:
>
> > raise Exception("Size of newly created file is %d, should have been %d"
>
> > %(fstat.st_size, dlen))
>
> > + if self.nfsversion >= 4:
>
> > + # revoke delegation
>
> > + self.dprint('DBG3', "revoke delegation")
>
> > + self.clientobj.run_cmd('chmod +x %s' % self.absfile)
>
> > +
>
> > if acregmax:
>
> > # Stat the unchanging file until acregmax is hit
>
> > # each stat doubles the valid cache time
>
> >
>
> >
>
>
>
parent reply other threads:[~2020-06-02 20:00 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <694b44377eae4adca7273de471807be7@G08CNEXMBPEKD05.g08.fujitsu.local>]
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=20200602200014.GD1769@fieldses.org \
--to=bfields@fieldses.org \
--cc=bfields@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=mora@netapp.com \
--cc=suyj.fnst@cn.fujitsu.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;
as well as URLs for NNTP newsgroup(s).