From: "J. Bruce Fields" <bfields@fieldses.org>
To: Peter Staubach <staubach@redhat.com>
Cc: NFS list <linux-nfs@vger.kernel.org>, Olaf Kirch <okir@suse.de>,
Andreas Gruenbacher <agruen@suse.de>
Subject: Re: [PATCH v2] register NFS_ACL with rpcbind
Date: Wed, 4 Nov 2009 13:58:48 -0500 [thread overview]
Message-ID: <20091104185848.GD11637@fieldses.org> (raw)
In-Reply-To: <4AEF562B.9070606@redhat.com>
On Mon, Nov 02, 2009 at 04:59:07PM -0500, Peter Staubach wrote:
> Hi.
>
> Here is a patch to modify the NFS server to register the NFS_ACL
> services with the rpcbind daemon. This allows the client to
> ping for the existence of the NFS_ACL support via commands such
> as "rpcinfo -t <server> nfs_acl".
>
> This patch also modifies the NFS_ACL support so that responses
> to version 2 NULLPROC requests can be made.
>
> The changelog for the patch which turned off this functionality
> mentioned something about not registering the NFS_ACL as being
> part of some tradition. I can't find this tradition and the
> only other implementation which supports NFS_ACL does register
> them with the rpcbind daemon.
>
> Thanx...
>
> ps
>
> Signed-off-by: Peter Staubach <staubach@redhat.com>
>
> --- linux-2.6.31.i686/fs/nfsd/nfs2acl.c.org
> +++ linux-2.6.31.i686/fs/nfsd/nfs2acl.c
> @@ -217,6 +217,16 @@ static int nfsaclsvc_decode_accessargs(s
> * XDR encode functions
> */
>
> +/*
> + * There must be an encoding function for void results so svc_process
> + * will work properly.
> + */
> +int
> +nfsaclsvc_encode_voidres(struct svc_rqst *rqstp, __be32 *p, void *dummy)
> +{
> + return xdr_ressize_check(rqstp, p);
> +}
Out of curiosity: have you tested a null rpc?
Also, doesn't v3 have the same problem?
--b.
> +
> /* GETACL */
> static int nfsaclsvc_encode_getaclres(struct svc_rqst *rqstp, __be32 *p,
> struct nfsd3_getaclres *resp)
> @@ -308,7 +318,6 @@ static int nfsaclsvc_release_access(stru
> }
>
> #define nfsaclsvc_decode_voidargs NULL
> -#define nfsaclsvc_encode_voidres NULL
> #define nfsaclsvc_release_void NULL
> #define nfsd3_fhandleargs nfsd_fhandle
> #define nfsd3_attrstatres nfsd_attrstat
> @@ -346,5 +355,5 @@ struct svc_version nfsd_acl_version2 = {
> .vs_proc = nfsd_acl_procedures2,
> .vs_dispatch = nfsd_dispatch,
> .vs_xdrsize = NFS3_SVC_XDRSIZE,
> - .vs_hidden = 1,
> + .vs_hidden = 0,
> };
> --- linux-2.6.31.i686/fs/nfsd/nfs3acl.c.org
> +++ linux-2.6.31.i686/fs/nfsd/nfs3acl.c
> @@ -264,6 +264,6 @@ struct svc_version nfsd_acl_version3 = {
> .vs_proc = nfsd_acl_procedures3,
> .vs_dispatch = nfsd_dispatch,
> .vs_xdrsize = NFS3_SVC_XDRSIZE,
> - .vs_hidden = 1,
> + .vs_hidden = 0,
> };
>
next prev parent reply other threads:[~2009-11-04 18:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-02 19:03 [PATCH] register NFS_ACL with rpcbind Peter Staubach
2009-11-02 21:59 ` [PATCH v2] " Peter Staubach
2009-11-03 9:13 ` Andreas Gruenbacher
2009-11-03 9:17 ` Olaf Kirch
2009-11-03 15:28 ` Peter Staubach
2009-11-03 15:34 ` Chuck Lever
2009-11-04 18:44 ` Peter Staubach
2009-11-04 19:45 ` Chuck Lever
2009-11-04 18:58 ` J. Bruce Fields [this message]
2009-11-04 19:54 ` Peter Staubach
2009-11-05 16:56 ` 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=20091104185848.GD11637@fieldses.org \
--to=bfields@fieldses.org \
--cc=agruen@suse.de \
--cc=linux-nfs@vger.kernel.org \
--cc=okir@suse.de \
--cc=staubach@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