public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Gruenbacher <agruen@suse.de>
To: Peter Staubach <staubach@redhat.com>
Cc: NFS list <linux-nfs@vger.kernel.org>,
	"J. Bruce Fields" <bfields@fieldses.org>,
	Olaf Kirch <okir@suse.de>
Subject: Re: [PATCH v2] register NFS_ACL with rpcbind
Date: Tue, 3 Nov 2009 10:13:27 +0100	[thread overview]
Message-ID: <200911031013.27247.agruen@suse.de> (raw)
In-Reply-To: <4AEF562B.9070606@redhat.com>

On Monday 02 November 2009 10:59:07 pm 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.

I don't understand the reasoning behind .vs_hidden for NFS_ACL, hopefully Olaf 
can clarify. NFS_ACL is the only user of .vs_hidden as far as I can see 
though, so if this is changeg, shouldn't the entire commit bc5fea4 which 
introduced the flag be reverted?

Thanks,
Andreas

  reply	other threads:[~2009-11-03  9:11 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 [this message]
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
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=200911031013.27247.agruen@suse.de \
    --to=agruen@suse.de \
    --cc=bfields@fieldses.org \
    --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