Searched hist:210455 (Results 1 - 9 of 9) sorted by relevance
| /freebsd-10-stable/sys/modules/nfslock/ | ||
| H A D | Makefile | 210455 Sat Jul 24 20:14:18 MDT 2010 rmacklem Move sys/nfsclient/nfs_lock.c into sys/nfs and build it as a separate module that can be used by both the regular and experimental nfs clients. This fixes the problem reported by jh@ where /dev/nfslock would be registered twice when both nfs clients were used. I also defined the size of the lm_fh field to be the correct value, as it should be the maximum size of an NFSv3 file handle. Reviewed by: jh MFC after: 2 weeks |
| /freebsd-10-stable/sys/modules/nfscl/ | ||
| H A D | Makefile | diff 210455 Sat Jul 24 20:14:18 MDT 2010 rmacklem Move sys/nfsclient/nfs_lock.c into sys/nfs and build it as a separate module that can be used by both the regular and experimental nfs clients. This fixes the problem reported by jh@ where /dev/nfslock would be registered twice when both nfs clients were used. I also defined the size of the lm_fh field to be the correct value, as it should be the maximum size of an NFSv3 file handle. Reviewed by: jh MFC after: 2 weeks |
| /freebsd-10-stable/sys/fs/nfsclient/ | ||
| H A D | nfs_clnfsiod.c | diff 210455 Sat Jul 24 20:14:18 MDT 2010 rmacklem Move sys/nfsclient/nfs_lock.c into sys/nfs and build it as a separate module that can be used by both the regular and experimental nfs clients. This fixes the problem reported by jh@ where /dev/nfslock would be registered twice when both nfs clients were used. I also defined the size of the lm_fh field to be the correct value, as it should be the maximum size of an NFSv3 file handle. Reviewed by: jh MFC after: 2 weeks |
| H A D | nfs_clsubs.c | diff 210455 Sat Jul 24 20:14:18 MDT 2010 rmacklem Move sys/nfsclient/nfs_lock.c into sys/nfs and build it as a separate module that can be used by both the regular and experimental nfs clients. This fixes the problem reported by jh@ where /dev/nfslock would be registered twice when both nfs clients were used. I also defined the size of the lm_fh field to be the correct value, as it should be the maximum size of an NFSv3 file handle. Reviewed by: jh MFC after: 2 weeks |
| /freebsd-10-stable/sys/nfs/ | ||
| H A D | nfs_lock.h | diff 210455 Sat Jul 24 20:14:18 MDT 2010 rmacklem Move sys/nfsclient/nfs_lock.c into sys/nfs and build it as a separate module that can be used by both the regular and experimental nfs clients. This fixes the problem reported by jh@ where /dev/nfslock would be registered twice when both nfs clients were used. I also defined the size of the lm_fh field to be the correct value, as it should be the maximum size of an NFSv3 file handle. Reviewed by: jh MFC after: 2 weeks |
| H A D | nfs_lock.c | diff 210455 Sat Jul 24 20:14:18 MDT 2010 rmacklem Move sys/nfsclient/nfs_lock.c into sys/nfs and build it as a separate module that can be used by both the regular and experimental nfs clients. This fixes the problem reported by jh@ where /dev/nfslock would be registered twice when both nfs clients were used. I also defined the size of the lm_fh field to be the correct value, as it should be the maximum size of an NFSv3 file handle. Reviewed by: jh MFC after: 2 weeks |
| /freebsd-10-stable/sys/modules/nfsclient/ | ||
| H A D | Makefile | diff 210455 Sat Jul 24 20:14:18 MDT 2010 rmacklem Move sys/nfsclient/nfs_lock.c into sys/nfs and build it as a separate module that can be used by both the regular and experimental nfs clients. This fixes the problem reported by jh@ where /dev/nfslock would be registered twice when both nfs clients were used. I also defined the size of the lm_fh field to be the correct value, as it should be the maximum size of an NFSv3 file handle. Reviewed by: jh MFC after: 2 weeks |
| /freebsd-10-stable/sys/nfsclient/ | ||
| H A D | nfs_nfsiod.c | diff 210455 Sat Jul 24 20:14:18 MDT 2010 rmacklem Move sys/nfsclient/nfs_lock.c into sys/nfs and build it as a separate module that can be used by both the regular and experimental nfs clients. This fixes the problem reported by jh@ where /dev/nfslock would be registered twice when both nfs clients were used. I also defined the size of the lm_fh field to be the correct value, as it should be the maximum size of an NFSv3 file handle. Reviewed by: jh MFC after: 2 weeks |
| H A D | nfs_vfsops.c | diff 210455 Sat Jul 24 20:14:18 MDT 2010 rmacklem Move sys/nfsclient/nfs_lock.c into sys/nfs and build it as a separate module that can be used by both the regular and experimental nfs clients. This fixes the problem reported by jh@ where /dev/nfslock would be registered twice when both nfs clients were used. I also defined the size of the lm_fh field to be the correct value, as it should be the maximum size of an NFSv3 file handle. Reviewed by: jh MFC after: 2 weeks |
Completed in 289 milliseconds