File open issue on 2.6.23 with NFS v4

[Frank Filz]

In testing security negotiation, I wanted to do some basic file I/O
tests to test the different permissions for different security flavors.
Along the way, I tried this old format /etc/exports:

/export/home gss/krb5(nohide,insecure,no_subtree_check,no_root_squash,async,rw)
/export      gss/krb5(fsid=0,insecure,no_subtree_check,no_root_squash,async,rw,crossmnt)

And I mount (from an AIX client):

mount -overs=4,sec=krb5 elm3a19.beaverton.ibm.com:/ /mnt-19

Then I attempt the following:

echo test >/mnt-19/test-aix

And it hangs, on the Linux server, I see the following NFS messages repeating:

Dec 13 16:54:57 elm3a19 kernel: NFSD: nfsd4_open filename test-aix op_stateowner 00000000
Dec 13 16:54:57 elm3a19 kernel: NFSD stale clientid (475f14c7/0000012a)
Dec 13 16:54:57 elm3a19 kernel: nfsd_dispatch: vers 4 proc 1
Dec 13 16:54:57 elm3a19 kernel: nfsv4 compound op #1: 22
Dec 13 16:54:57 elm3a19 kernel: nfsd: fh_verify(8: 00010001 00000000 00000000 00000000 00000000 00000000)
Dec 13 16:54:57 elm3a19 kernel: nfsv4 compound op #2: 9
Dec 13 16:54:57 elm3a19 kernel: nfsd: fh_verify(8: 00010001 00000000 00000000 00000000 00000000 00000000)
Dec 13 16:54:57 elm3a19 kernel: nfsd: fh_verify - just checking
Dec 13 16:54:57 elm3a19 kernel: nfsv4 compound op #3: 15
Dec 13 16:54:57 elm3a19 kernel: nfsd: nfsd_lookup(fh 8: 00010001 00000000 00000000 00000000 00000000 00000000, test-aix)
Dec 13 16:54:57 elm3a19 kernel: nfsd: fh_verify(8: 00010001 00000000 00000000 00000000 00000000 00000000)
Dec 13 16:54:57 elm3a19 kernel: nfsd: fh_verify - just checking
Dec 13 16:54:57 elm3a19 kernel: nfsd: fh_lock(8: 00010001 00000000 00000000 00000000 00000000 00000000) locked = 0
Dec 13 16:54:57 elm3a19 kernel: nfsd_dispatch: vers 4 proc 1
Dec 13 16:54:57 elm3a19 kernel: nfsv4 compound op #1: 22
Dec 13 16:54:57 elm3a19 kernel: nfsd: fh_verify(8: 00010001 00000000 00000000 00000000 00000000 00000000)
Dec 13 16:54:57 elm3a19 kernel: nfsv4 compound op #2: 32
Dec 13 16:54:58 elm3a19 kernel: nfsv4 compound op #3: 18

Any thoughts as to what might be wrong?

Thanks

Frank