Searched hist:49405 (Results 1 - 3 of 3) sorted by relevance
| /freebsd-10.3-release/sys/nfs/ | ||
| H A D | nfs_common.h | diff 49405 Wed Aug 04 14:41:39 MDT 1999 peter Don't over-allocate and over-copy shorter NFSv2 filehandles and then correct the pointers afterwards. It's kinda bogus that we generate a 24 (?) byte filehandle (2 x int32 fsid and 16 byte VFS fhandle) and pad it out to 64 bytes for NFSv3 with garbage. The whole point of NFSv3's variable filehandle length was to allow for shorter handles, both in memory and over the wire. I plan on taking a shot at fixing this shortly. |
| /freebsd-10.3-release/sys/nfsclient/ | ||
| H A D | nfsm_subs.h | diff 49405 Wed Aug 04 14:41:39 MDT 1999 peter Don't over-allocate and over-copy shorter NFSv2 filehandles and then correct the pointers afterwards. It's kinda bogus that we generate a 24 (?) byte filehandle (2 x int32 fsid and 16 byte VFS fhandle) and pad it out to 64 bytes for NFSv3 with garbage. The whole point of NFSv3's variable filehandle length was to allow for shorter handles, both in memory and over the wire. I plan on taking a shot at fixing this shortly. |
| /freebsd-10.3-release/sys/nfsserver/ | ||
| H A D | nfsm_subs.h | diff 49405 Wed Aug 04 14:41:39 MDT 1999 peter Don't over-allocate and over-copy shorter NFSv2 filehandles and then correct the pointers afterwards. It's kinda bogus that we generate a 24 (?) byte filehandle (2 x int32 fsid and 16 byte VFS fhandle) and pad it out to 64 bytes for NFSv3 with garbage. The whole point of NFSv3's variable filehandle length was to allow for shorter handles, both in memory and over the wire. I plan on taking a shot at fixing this shortly. |
Completed in 61 milliseconds