Hi Steve-
As I understand it, the documented bug refers to running nfs-utils
1.1.3 on kernels older than 2.6.22 (ie the problem is with the legacy
mount command, not with the in-kernel mount parser, which has a
different, less harmful bug that masks these symptoms).
To reproduce this you need to force the use of the legacy mount
command that parses mount options in user space and passes a binary
data structure to the kernel via mount(2).
On Oct 2, 2008, at Oct 2, 2008, 9:27 AM, Steve Dickson wrote:
What is logged in /var/log/messages you turn on the in-kernel mount
debugging via:
rpcdebug -m nfs -s mount
then do the following three mounts:
mount -o sec=none madhat:/home /mnt/home
mount -o sec=sys madhat:/home /mnt/home
mount madhat:/home /mnt/home
I got:
Oct 2 09:23:10 rawhat kernel: NFS: nfs mount
opts='sec=none,addr=10.16.60.33'
Oct 2 09:23:10 rawhat kernel: NFS: parsing nfs mount option
'sec=none'
Oct 2 09:23:10 rawhat kernel: NFS: parsing nfs mount option
'addr=10.16.60.33'
Oct 2 09:23:10 rawhat kernel: NFS: sending MNT request for madhat:/
home
Oct 2 09:23:10 rawhat kernel: NFS: MNT request succeeded
Oct 2 09:23:43 rawhat kernel: NFS: nfs mount
opts='sec=sys,addr=10.16.60.33'
Oct 2 09:23:43 rawhat kernel: NFS: parsing nfs mount option
'sec=sys'
Oct 2 09:23:43 rawhat kernel: NFS: parsing nfs mount option
'addr=10.16.60.33'
Oct 2 09:23:43 rawhat kernel: NFS: sending MNT request for madhat:/
home
Oct 2 09:23:43 rawhat kernel: NFS: MNT request succeeded
Oct 2 09:24:00 rawhat kernel: NFS: nfs mount opts='addr=10.16.60.33'
Oct 2 09:24:00 rawhat kernel: NFS: parsing nfs mount option
'addr=10.16.60.33'
Oct 2 09:24:00 rawhat kernel: NFS: sending MNT request for madhat:/
home
Oct 2 09:24:00 rawhat kernel: NFS: MNT request succeeded
steved.
--
Chuck Lever
chuck[dot]lever[at]oracle[dot]com
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
