From: Mi Jinlong <mijinlong@cn.fujitsu.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: NFSv3 list <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] NFS4.1: Fix bug server don't reply the right fore_channel to client at create_session
Date: Mon, 15 Nov 2010 16:12:43 +0800 [thread overview]
Message-ID: <4CE0EB7B.5060509@cn.fujitsu.com> (raw)
In-Reply-To: <20101112204554.GF32745@fieldses.org>
J. Bruce Fields:
> On Thu, Nov 11, 2010 at 06:03:40PM +0800, Mi Jinlong wrote:
>> At the latest kernel(2.6.37-rc1), server just initialize the forechannel
>> at init_forechannel_attrs, but don't reflect it to reply.
>>
>> After initialize the session success, we should copy the forechannel info
>> to nfsd4_create_session struct.
>
> Thanks!
>
> Is there a chance you could write a pynfs test for this?
Maybe the following one is OK.
------------
SRVR: Can server return fore_channel maxreqs correctly
When client set the fore_channel maxreqs larger than server's
NFSD_MAX_SLOTS_PER_SESSION at create_sessino, the fore_channel
maxreqs at the reply must less than NFSD_MAX_SLOTS_PER_SESSION.
At 2.6.37-rc1, the NFSD_MAX_SLOTS_PER_SESSION is 160.
Signed-off-by: Mi Jinlong <mijinlong@cn.fujitsu.com>
---
nfs4.1/server41tests/st_create_session.py | 19 +++++++++++++++++++
1 files changed, 19 insertions(+), 0 deletions(-)
diff --git a/nfs4.1/server41tests/st_create_session.py b/nfs4.1/server41tests/st_create_session.py
index 5f425d4..174d31e 100644
--- a/nfs4.1/server41tests/st_create_session.py
+++ b/nfs4.1/server41tests/st_create_session.py
@@ -156,6 +156,25 @@ def testReplay1b(t, env):
if not nfs4lib.test_equal(res1, res2):
fail("Replay results not equal")
+def testReplay1c(t, env):
+ """Replay a successful CREATE_SESSION with right maxreqs
+ (less than NFSD_MAX_SLOTS_PER_SESSION)
+
+ FLAGS: create_session all
+ CODE: CSESS5c
+ """
+ NFSD_MAX_SLOTS_PER_SESSION = 160
+
+ c = env.c1.new_client(env.testname(t))
+ # CREATE_SESSION with fore_channel = NFSD_MAX_SLOTS_PER_SESSION + 1
+ chan_attrs = channel_attrs4(0,8192,8192,8192,128,
+ NFSD_MAX_SLOTS_PER_SESSION + 1,[])
+ sess1 = c.create_session(fore_attrs=chan_attrs)
+
+ if nfs4lib.test_equal(sess1.fore_channel.maxrequests,
+ chan_attrs.ca_maxrequests, "count4"):
+ fail("Replay wrong fore_channel maxreqs")
+
def testReplay2(t, env):
"""Replay a unsuccessful CREATE_SESSION
--
1.7.3.2
next prev parent reply other threads:[~2010-11-15 8:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-11 10:03 [PATCH] NFS4.1: Fix bug server don't reply the right fore_channel to client at create_session Mi Jinlong
2010-11-11 13:32 ` Benny Halevy
2010-11-12 20:45 ` J. Bruce Fields
2010-11-15 8:12 ` Mi Jinlong [this message]
2010-12-29 19:35 ` J. Bruce Fields
2010-12-30 3:16 ` Mi Jinlong
2011-01-05 1:00 ` J. Bruce Fields
2011-01-05 5:56 ` Mi Jinlong
2011-01-05 17:35 ` 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=4CE0EB7B.5060509@cn.fujitsu.com \
--to=mijinlong@cn.fujitsu.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 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.