From: "J. Bruce Fields" <bfields@fieldses.org>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: "J. Bruce Fields" <bfields@redhat.com>,
Steve Dickson <steved@redhat.com>,
Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 2/2] NFSDv4.2: Added NFS v4.2 support to the NFS server
Date: Fri, 22 Feb 2013 10:38:01 -0500 [thread overview]
Message-ID: <20130222153801.GD20588@fieldses.org> (raw)
In-Reply-To: <4FA345DA4F4AE44899BD2B03EEEC2FA9235DBFBA@SACEXCMBX04-PRD.hq.netapp.com>
On Fri, Feb 22, 2013 at 03:30:08PM +0000, Myklebust, Trond wrote:
> On Fri, 2013-02-22 at 10:26 -0500, J. Bruce Fields wrote:
> > On Thu, Feb 21, 2013 at 05:15:11PM -0500, Steve Dickson wrote:
> > > This enable NFSv4.2 support for the server. To enable this
> > > code do the following:
> > > echo "+4.2" >/proc/fs/nfsd/versions
> > >
> > > after the nfsd kernel module is loaded.
> > >
> > > Signed-off-by: Steve Dickson <steved@redhat.com>
> > > ---
> > > fs/nfsd/nfs4xdr.c | 1 +
> > > fs/nfsd/nfsd.h | 2 +-
> > > 2 files changed, 2 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/fs/nfsd/nfs4xdr.c b/fs/nfsd/nfs4xdr.c
> > > index d2ae8db..86be853 100644
> > > --- a/fs/nfsd/nfs4xdr.c
> > > +++ b/fs/nfsd/nfs4xdr.c
> > > @@ -1621,6 +1621,7 @@ struct nfsd4_minorversion_ops {
> > > static struct nfsd4_minorversion_ops nfsd4_minorversion[] = {
> > > [0] = { nfsd4_dec_ops, ARRAY_SIZE(nfsd4_dec_ops) },
> > > [1] = { nfsd41_dec_ops, ARRAY_SIZE(nfsd41_dec_ops) },
> > > + [2] = { nfsd41_dec_ops, ARRAY_SIZE(nfsd41_dec_ops) },
> > > };
> > >
> > > static __be32
> > > diff --git a/fs/nfsd/nfsd.h b/fs/nfsd/nfsd.h
> > > index 26a457b..0e3ccd1 100644
> > > --- a/fs/nfsd/nfsd.h
> > > +++ b/fs/nfsd/nfsd.h
> > > @@ -24,7 +24,7 @@
> > > /*
> > > * nfsd version
> > > */
> > > -#define NFSD_SUPPORTED_MINOR_VERSION 1
> > > +#define NFSD_SUPPORTED_MINOR_VERSION 2
> > > /*
> > > * Maximum blocksizes supported by daemon under various circumstances.
> > > */
> >
> > Looks OK to me, except this should be behind a config for now.
> >
> > On a grep for "minorversion" I notice two oversights, below: one just a
> > comment, one might result in getting the wrong minorversion on
> > callbacks.
> >
> > --b.
> >
> > diff --git a/fs/nfsd/nfs4state.c b/fs/nfsd/nfs4state.c
> > index 503e15e..b86cf07 100644
> > --- a/fs/nfsd/nfs4state.c
> > +++ b/fs/nfsd/nfs4state.c
> > @@ -1665,7 +1665,7 @@ out_new:
> > status = nfserr_jukebox;
> > goto out;
> > }
> > - new->cl_minorversion = 1;
> > + new->cl_minorversion = cstate->minorversion;
> >
> > gen_clid(new);
> > add_to_unconfirmed(new, strhashval);
> > diff --git a/fs/nfsd/state.h b/fs/nfsd/state.h
> > index e036894..28d41ef 100644
> > --- a/fs/nfsd/state.h
> > +++ b/fs/nfsd/state.h
> > @@ -108,7 +108,7 @@ struct nfs4_cb_conn {
> > u32 cb_prog; /* used only in 4.0 case;
> > per-session otherwise */
> > u32 cb_ident; /* minorversion 0 only */
> > - struct svc_xprt *cb_xprt; /* minorversion 1 only */
> > + struct svc_xprt *cb_xprt; /* minorversion >=1 only */
>
> Tagging things as being particlar to a give minorversion means that
> we'll never stop having to change the comments.
I don't see how "minorversion >=1 only" is likely to become untrue. Are
we really expecting to remove the session back channel in a future minor
version?
> Why not just label it as being the session back channel?
I don't really care. Happy to take alternate text if you want to
suggest something.
--b.
next prev parent reply other threads:[~2013-02-22 15:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-21 22:15 [PATCH 0/2] NFS v4.2 support to both the server and client Steve Dickson
2013-02-21 22:15 ` [PATCH 1/2] NFSv4.2: Added NFS v4.2 support to the NFS client Steve Dickson
2013-02-21 22:22 ` Myklebust, Trond
2013-02-21 23:13 ` Steve Dickson
2013-02-22 15:28 ` J. Bruce Fields
2013-02-22 15:34 ` Myklebust, Trond
2013-02-22 15:13 ` J. Bruce Fields
2013-02-22 16:38 ` Steve Dickson
2013-02-22 16:58 ` J. Bruce Fields
2013-02-22 17:01 ` Steve Dickson
2013-02-21 22:15 ` [PATCH 2/2] NFSDv4.2: Added NFS v4.2 support to the NFS server Steve Dickson
2013-02-22 15:26 ` J. Bruce Fields
2013-02-22 15:30 ` Myklebust, Trond
2013-02-22 15:38 ` J. Bruce Fields [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-02-22 8:47 [PATCH 0/2] NFS v4.2 support to both the server and client (take 2) Steve Dickson
2013-02-22 8:47 ` [PATCH 2/2] NFSDv4.2: Added NFS v4.2 support to the NFS server Steve Dickson
2013-02-22 14:34 [PATCH 0/2] NFS v4.2 support to both the server and client (take 3) Steve Dickson
2013-02-22 14:34 ` [PATCH 2/2] NFSDv4.2: Added NFS v4.2 support to the NFS server Steve Dickson
2013-02-22 17:09 [PATCH 0/2] NFS v4.2 support to both the server and client (take 4) Steve Dickson
2013-02-22 17:09 ` [PATCH 2/2] NFSDv4.2: Added NFS v4.2 support to the NFS server Steve Dickson
2013-02-22 18:05 ` J. Bruce Fields
2013-02-22 18:10 ` J. Bruce Fields
2013-02-23 14:49 ` Steve Dickson
2013-02-23 12:43 ` Steve Dickson
2013-02-23 13:00 ` J. Bruce Fields
2013-02-23 13:01 ` 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=20130222153801.GD20588@fieldses.org \
--to=bfields@fieldses.org \
--cc=Trond.Myklebust@netapp.com \
--cc=bfields@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=steved@redhat.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).