From: "J. Bruce Fields" <bfields@fieldses.org>
To: "Ed V. Bartosh" <ed@sam-solutions.net>
Cc: nfs@lists.sourceforge.net
Subject: Re: NFSv3 UID/GID mapping
Date: Thu, 22 Apr 2004 13:25:12 -0400 [thread overview]
Message-ID: <20040422172512.GE12400@fieldses.org> (raw)
In-Reply-To: <m3vfjsxsky.fsf@pc213.belcaf.minsk.by>
On Thu, Apr 22, 2004 at 12:36:13PM +0300, Ed V. Bartosh wrote:
> Here is the NFSv3 uid/gid mapping implementation (both kernel and
> nfs-utils parts). Userspace part uses idmap daemon from CITI NFSv4,
> so the NFSv4 patches are required.
Just out of curiosity:
* This does the server side only. Have you looked at the client side
at all?
* What sort of applications are you considering for this?
> Look at this, please. Any kind of feedback will be appreciated.
Do you also need to do map the id's in nfs3xdr.c:xdr_encode_setattr() and
xdr_decode_fattr()?
Is IDMAP_UID_NONE really needed, or could you just use an ENOENT return?
We need to figure out a way to do this without duplicating so much code
from nfs4idmap.c.
Also note some of that code is wrong. (See the nfsd_idmap patches in
http://www.citi.umich.edu/projects/nfsv4/linux/kernel-patches/2.6.6-rc1-3/).
--Bruce Fields
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2004-04-22 17:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-22 9:36 NFSv3 UID/GID mapping Ed V. Bartosh
2004-04-22 17:25 ` J. Bruce Fields [this message]
2004-04-23 9:12 ` Ed V. Bartosh
2004-04-23 18:23 ` 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=20040422172512.GE12400@fieldses.org \
--to=bfields@fieldses.org \
--cc=ed@sam-solutions.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox