From: Eric Whiting <ewhiting@amis.com>
To: "nfs@lists.sourceforge.net" <nfs@lists.sourceforge.net>
Subject: nobody -2 problems linux nfs client -- VMS multinet NFS server
Date: Wed, 26 Jun 2002 11:14:16 -0600 [thread overview]
Message-ID: <3D19F668.B62C14D8@amis.com> (raw)
I think I'm seeing a uid wrap/overflow problem in the linux nfs client
or userid libc stuff -- but it might be in the VMS NFS server...
SERVER: VMS multinet NFS server
CLIENT: 2.2.18 linux works ok with the 'nobody' account.
nobody@ogre:/home/falcon > ls -la |grep phurst
dr-x------ 2 nobody nogroup 199680 Jun 26 11:07 phurst
I can list this dir and access files in it.
CLIENT: 2.4.18 linux doesn't work with the 'nobody' account.
nobody@teton:/home/falcon> id
uid=65534(nobody) gid=65534(nogroup) groups=65534(nogroup),65533(nobody)
nobody@teton:/home/falcon> ls -la |grep phurst
dr-x------ 2 4294967294 4294967294 199680 Jun 26 11:07 phurst
In this case the nobody account appears to go across as a -2 and the use
of long int instead of short int somewhere is bouncing the uid/gid
values up to the 4294967294 uid/gid number.. which causes some problems.
Anyone else seeing this? Is this a linux NFS fix that is showing a
multinet bug?
eric
Here is a tcpdump showing the -2/-2 stuff.
teton:~ # tcpdump host pleiad
tcpdump: listening on eth0
11:12:07.657523 teton.2306391190 > tyco.nfs: 108 getattr [|nfs] (DF)
11:12:07.657987 tyco.nfs > teton.2306391190: reply ok 96 getattr DIR
40755 ids -2/-2 sz 1536
11:12:07.658160 teton.2323168406 > tyco.nfs: 108 getattr [|nfs] (DF)
11:12:07.658649 tyco.nfs > teton.2323168406: reply ok 96 getattr DIR
40755 ids -2/-2 sz 1536
-------------------------------------------------------
This sf.net email is sponsored by: Jabber Inc.
Don't miss the IM event of the season | Special offer for OSDN members!
JabberConf 2002, Aug. 20-22, Keystone, CO http://www.jabberconf.com/osdn
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
reply other threads:[~2002-06-26 17:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3D19F668.B62C14D8@amis.com \
--to=ewhiting@amis.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.