All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Marc Eshel <eshel@almaden.ibm.com>
Cc: Linux NFS Mailing List <nfs@lists.sourceforge.net>
Subject: Re: lockd GRANT_MSG RPC callback
Date: Thu, 9 Sep 2004 14:50:14 -0400	[thread overview]
Message-ID: <20040909185014.GA14863@fieldses.org> (raw)
In-Reply-To: <OFB813A46E.D2D0BEF5-ON88256F0A.00644E81-88256F0A.0064C59E@us.ibm.com>

On Thu, Sep 09, 2004 at 11:20:41AM -0700, Marc Eshel wrote:
> "J. Bruce Fields" <bfields@fieldses.org> wrote on 09/09/2004 05:56:25 AM:
> 
> > On Thu, Sep 09, 2004 at 01:08:36PM +1000, Greg Banks wrote:
> > > On Thu, 2004-09-09 at 06:50, Trond Myklebust wrote:
> > > > OK. Bruce has promised to work on splitting out the "domain" code
> from
> > > > the svcauth_unix code. Once that is done, we can fix up GRANT_MSG and
> > > > NOTIFY as well as any other routines that do not need to be
> > > > authenticated by rpc.mountd.
> > >
> > > Any idea how long is this likely to take?
> 
> > I'll try to have something out by early next week.
> 
> > The problem is that the server-side rpc code is checking *all* incoming
> > auth_unix and auth_null requests (whether for nfsd or for some other
> > service) against the exports table.  So as a temporary workaround, lockd
> > will work if the client lists the server in the exports file.  Or
> > something like
> 
> It worked only after I mounted a client export on the server side.
> 
> > echo nfsd server.ip.address.here 0x7FFFFFFF server.name.here \
> > >/proc/net/rpc/auth.unix.ip/content
> >
> > may also work, though the entry you add to the auth.unix.ip cache by
> > doing this may end up getting purged next time you run exportfs.
> 
> It doesn't look like you can write to /proc/net/rpc/auth.unix.ip/content.

Have you mounted the nfsd filesystem at /proc/fs/nfs/?  (See the
exportfs(8) man page.)

--Bruce Fields


-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM. 
Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2004-09-09 18:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <OFAF6A9C4E.27A9BF20-ON88256EFB.00020035-88256EFB.0002DABA@LocalDomain>
2004-09-08 17:33 ` lockd GRANT_MSG RPC callback Marc Eshel
2004-09-08 18:24   ` Trond Myklebust
2004-09-08 19:49     ` Marc Eshel
2004-09-08 20:12       ` Trond Myklebust
2004-09-08 20:35         ` Marc Eshel
2004-09-08 20:50           ` Trond Myklebust
2004-09-09  3:08             ` Greg Banks
2004-09-09 12:56               ` J. Bruce Fields
2004-09-09 18:20                 ` Marc Eshel
2004-09-09 18:50                   ` J. Bruce Fields [this message]
2004-09-10  2:51                 ` Greg Banks
2004-09-10 16:22                   ` Trond Myklebust
2004-09-13  4:08                     ` Greg Banks

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=20040909185014.GA14863@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=eshel@almaden.ibm.com \
    --cc=nfs@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.