Linux NFS development
 help / color / mirror / Atom feed
From: "Frank Filz" <ffilzlnx@mindspring.com>
To: "'J. Bruce Fields'" <bfields@fieldses.org>
Cc: "'Kinglong Mee'" <kinglongmee@gmail.com>,
	<linux-nfs@vger.kernel.org>, <tigran.mkrtchyan@desy.de>
Subject: RE: [PATCH 4/4] 4.1 create_session: Skip test of CB_NULL for nfs4.1
Date: Tue, 28 Jul 2015 12:55:26 -0700	[thread overview]
Message-ID: <009b01d0c96f$5c0a5c00$141f1400$@mindspring.com> (raw)
In-Reply-To: <20150728194730.GE20951@fieldses.org>

> On Tue, Jul 28, 2015 at 11:16:21AM -0700, Frank Filz wrote:
> > > On Tue, Jul 28, 2015 at 09:03:38AM -0700, Frank Filz wrote:
> > > > Why are we removing these two test cases? The Ganesha NFS server
> > > > at
> > > least passes them.
> > >
> > > And there's nothing wrong with passing the tests, but unfortunately
> > there's
> > > not necessarily anything wrong with failing either: a 4.1 server
> > > isn't
> > required
> > > to do a NULL callback to probe the backchannel.
> > >
> > > There might be a better test (depend on delegation recalls instead
> > > of CB_NULL's?), till then I'm OK with turning them off by default.
> >
> > I guess I'd at least like to see some explanation of why we're turning
> > the tests off by default. I'm just resistant to removing testing for no
reason.
> 
> The story is: we turned off the CB_NULL probe in knfsd in the 4.1 case;
it's
> unnecessary, and it was causing some problems (due partly to other bugs,
> but why ask for trouble?).  So these tests started failing.  I'd fix the
server if
> there was an actual bug, but it's the tests that are wrong in this case,
so oh
> well.

Ah, ok. I'd love to understand the issues there better, maybe Ganesha
shouldn't be doing the CB_NULL either...

> > If the test doesn't actually test anything useful, that would be one
> > explanation.
> >
> > If it's something that's not required and not all servers do it, then
> > that's another explanation.
> 
> Right, this is it, CB_NULL probes aren't required.

Ok, with this perspective, I'm cool with the test being removed from
default.

> We're testing something useful, but something you need a callback to test,
> so trying to get some other kind of callback (like a deleg recall) would
be
> another option.

Hmm, more to think about from testing Ganesha perspective. The "simple"
thing  (i.e. using FSAL_VFS) to test in Ganesha doesn't do delegations, so
the CB_NULL might be the only callback it makes, which might make it
somewhat useful to prove Ganesha's callback code isn't totally broken...

Thanks for the additional explanation.

Frank

> > There might be other explanations, just please give some insight.
> >
> > Thanks
> >
> > Frank
> >
> > > > > -----Original Message-----
> > > > > From: linux-nfs-owner@vger.kernel.org [mailto:linux-nfs-
> > > > > owner@vger.kernel.org] On Behalf Of Kinglong Mee
> > > > > Sent: Tuesday, July 28, 2015 4:47 AM
> > > > > To: J. Bruce Fields; linux-nfs@vger.kernel.org
> > > > > Cc: tigran.mkrtchyan@desy.de; kinglongmee@gmail.com
> > > > > Subject: [PATCH 4/4] 4.1 create_session: Skip test of CB_NULL
> > > > > for
> > > > > nfs4.1
> > > > >
> > > > > Signed-off-by: Kinglong Mee <kinglongmee@gmail.com>
> > > > > ---
> > > > >  nfs4.1/server41tests/st_create_session.py | 4 ++--
> > > > >  1 file changed, 2 insertions(+), 2 deletions(-)
> > > > >
> > > > > diff --git a/nfs4.1/server41tests/st_create_session.py
> > > > > b/nfs4.1/server41tests/st_create_session.py
> > > > > index b42e0ab..4c56bb4 100644
> > > > > --- a/nfs4.1/server41tests/st_create_session.py
> > > > > +++ b/nfs4.1/server41tests/st_create_session.py
> > > > > @@ -333,7 +333,7 @@ def testManyClients(t, env):
> > > > >  def testCallbackProgram(t, env):
> > > > >      """Check server can handle random transient program number
> > > > >
> > > > > -    FLAGS: create_session all
> > > > > +    FLAGS:
> > > > >      CODE: CSESS20
> > > > >      """
> > > > >      cb_occurred = threading.Event() @@ -360,7 +360,7 @@ def
> > > > > testCallbackProgram(t, env):
> > > > >  def testCallbackVersion(t, env):
> > > > >      """Check server sends callback program with a version
> > > > > listed in nfs4client.py
> > > > >
> > > > > -    FLAGS: create_session all
> > > > > +    FLAGS:
> > > > >      CODE: CSESS21
> > > > >      """
> > > > >      cb_occurred = threading.Event()
> > > > > --
> > > > > 2.4.3
> > > > >
> > > > > --
> > > > > To unsubscribe from this list: send the line "unsubscribe
linux-nfs"
> > > > > in the body of a message to majordomo@vger.kernel.org More
> > > majordomo
> > > > > info at http://vger.kernel.org/majordomo-info.html
> > > --
> > > To unsubscribe from this list: send the line "unsubscribe linux-nfs"
> > > in
> > the
> > > body of a message to majordomo@vger.kernel.org More majordomo
> info
> > > at http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2015-07-28 19:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-28 11:46 [PATCH 4/4] 4.1 create_session: Skip test of CB_NULL for nfs4.1 Kinglong Mee
2015-07-28 16:03 ` Frank Filz
2015-07-28 17:58   ` 'J. Bruce Fields'
2015-07-28 18:16     ` Frank Filz
2015-07-28 19:47       ` 'J. Bruce Fields'
2015-07-28 19:55         ` Frank Filz [this message]
2015-07-29 19:15           ` '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='009b01d0c96f$5c0a5c00$141f1400$@mindspring.com' \
    --to=ffilzlnx@mindspring.com \
    --cc=bfields@fieldses.org \
    --cc=kinglongmee@gmail.com \
    --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