linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Tigran Mkrtchyan <tigran.mkrtchyan@desy.de>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH] generic currentstateid test of should not require pnfs-aware session
Date: Wed, 22 Jul 2020 10:11:24 -0400	[thread overview]
Message-ID: <20200722141124.GB28219@fieldses.org> (raw)
In-Reply-To: <20200721191628.16970-1-tigran.mkrtchyan@desy.de>

On Tue, Jul 21, 2020 at 09:16:28PM +0200, Tigran Mkrtchyan wrote:
> CSID8 doesn't depend on pnfs capability of a server, thus should not
> create pnfs-aware session.

Thanks!--b.

> 
> Signed-off-by: Tigran Mkrtchyan <tigran.mkrtchyan@desy.de>
> ---
>  nfs4.1/server41tests/st_current_stateid.py | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/nfs4.1/server41tests/st_current_stateid.py b/nfs4.1/server41tests/st_current_stateid.py
> index 8882e96..6480ae9 100644
> --- a/nfs4.1/server41tests/st_current_stateid.py
> +++ b/nfs4.1/server41tests/st_current_stateid.py
> @@ -164,7 +164,7 @@ def testOpenSetattr(t, env):
>      CODE: CSID8
>      """
>      size = 8
> -    sess = env.c1.new_pnfs_client_session(env.testname(t))
> +    sess = env.c1.new_client_session(env.testname(t))
>  
>      open_op = open_create_file_op(sess, env.testname(t), open_create=OPEN4_CREATE)
>      res = sess.compound( open_op +
> -- 
> 2.26.2

      reply	other threads:[~2020-07-22 14:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-21 19:16 [PATCH] generic currentstateid test of should not require pnfs-aware session Tigran Mkrtchyan
2020-07-22 14:11 ` J. Bruce Fields [this message]

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=20200722141124.GB28219@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=tigran.mkrtchyan@desy.de \
    /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).