summaryrefslogtreecommitdiffstats
path: root/sys/fs/nfsclient/nfs_clsubs.c
Commit message (Collapse)AuthorAgeFilesLines
* MFC r303710:kib2016-08-101-27/+6
| | | | | | | Remove unneeded (recursing) Giant acquisition around vprintf(9). MFC r303715: Remove ncl_printf(), use printf(9) directly.
* Replace the MNT_VNODE_FOREACH interface with MNT_VNODE_FOREACH_ALL.mckusick2012-04-171-10/+1
| | | | | | | | | | | | | | | | | | | | | The primary changes are that the user of the interface no longer needs to manage the mount-mutex locking and that the vnode that is returned has its mutex locked (thus avoiding the need to check to see if its is DOOMED or other possible end of life senarios). To minimize compatibility issues for third-party developers, the old MNT_VNODE_FOREACH interface will remain available so that this change can be MFC'ed to 9. Following the MFC to 9, MNT_VNODE_FOREACH will be removed in head. The reason for this update is to prepare for the addition of the MNT_VNODE_FOREACH_ACTIVE interface that will loop over just the active vnodes associated with a mount point (typically less than 1% of the vnodes associated with the mount point). Reviewed by: kib Tested by: Peter Holm MFC after: 2 weeks
* Simple find/replace of VOP_ISLOCKED -> NFSVOPISLOCKED. This is done so that ↵zack2011-07-161-1/+1
| | | | | | | | NFSVOPISLOCKED can be modified later to add enhanced logging and assertions. Reviewed by: rmacklem Approved by: zml (mentor) MFC after: 2 weeks
* Simple find/replace of vn_lock -> NFSVOPLOCK. This is done so that ↵zack2011-07-161-2/+2
| | | | | | | | NFSVOPLOCK can be modified later to add enhanced logging and assertions. Reviewed by: rmacklem Approved by: zml (mentor) MFC after: 2 weeks
* Add DTrace support to the new NFS client. This is essentiallyrmacklem2011-06-181-0/+5
| | | | | | | cloned from the old NFS client, plus additions for NFSv4. A review of this code is in progress, however it was felt by the reviewer that it could go in now, before code slush. Any changes required by the review can be committed as bug fixes later.
* Change the sysctl naming for the old and new NFS clientsrmacklem2011-05-151-2/+2
| | | | | to vfs.oldnfs.xxx and vfs.nfs.xxx respectively. This makes the default nfs client use vfs.nfs.xxx after r221124.
* In ncl_printf(), call vprintf() instead of printf().ru2011-05-041-1/+1
| | | | MFC after: 3 days
* Change the experimental NFS client so that it creates nfsiodrmacklem2011-04-151-3/+7
| | | | | | | | | threads in the same manner as the regular NFS client after r214026 was committed. This resolves the lors fixed by r214026 and its predecessors for the regular client. Reviewed by: jhb MFC after: 2 weeks
* Modify the return value for nfscl_mustflush() from boolean_t,rmacklem2010-08-031-3/+2
| | | | | | | | which I mistakenly thought was correct w.r.t. style(9), back to int and add the checks for != 0. This is just a stylistic modification. MFC after: 1 week
* Move sys/nfsclient/nfs_lock.c into sys/nfs and build it as a separatermacklem2010-07-241-1/+0
| | | | | | | | | | | 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
* Change the nfscl_mustflush() function in the experimental NFSv4rmacklem2010-07-181-2/+3
| | | | | | | client to return a boolean_t in order to make it more compatible with style(9). MFC after: 2 weeks
* For the experimental NFSv4 client, do not use cached attributesrmacklem2010-07-131-1/+1
| | | | | | that were invalidated, even when a delegation for the file is held. MFC after: 2 weeks
* In NFS clients, instead of inconsistently using #ifdefkib2010-06-131-8/+2
| | | | | | | | DIAGNOSTIC and #ifndef DIAGNOSTIC for debug assertions, prefer KASSERT(). Also change one #ifdef DIAGNOSTIC in the new nfs server. Submitted by: Mikolaj Golub <to.my.trociny gmail com> MFC after: 2 weeks
* Allow the experimental NFSv4 client to use cached attributesrmacklem2010-05-181-2/+7
| | | | | | | when a write delegation is held. Also, add a missing mtx_unlock() call for the ACL debugging code. MFC after: 5 days
* Patch the experimental NFS client in a manner analogous tormacklem2010-01-281-3/+3
| | | | | | | | r203072 for the regular NFS client. Also, delete two fields of struct nfsmount that are not used by the FreeBSD port of the client. MFC after: 2 weeks
* Unloading of the nfscl module is unsupported because newnfslock doesn'tjh2009-10-201-0/+7
| | | | | | | | | support unloading. It's not trivial to implement newnfslock unloading so for now just admit that unloading is unsupported and refuse to attempt unload in all nfscl module event handlers. Reviewed by: rmacklem Approved by: trasz (mentor)
* Apply the same patch as r196205 for nfs_upgrade_lock() andrmacklem2009-08-171-15/+12
| | | | | | nfs_downgrade_lock() to the experimental nfs client. Approved by: re (kensmith), kib (mentor)
* Add the experimental nfs subtree to the kernel, that includesrmacklem2009-05-041-0/+402
support for NFSv4 as well as NFSv2 and 3. It lives in 3 subdirs under sys/fs: nfs - functions that are common to the client and server nfsclient - a mutation of sys/nfsclient that call generic functions to do RPCs and handle state. As such, it retains the buffer cache handling characteristics and vnode semantics that are found in sys/nfsclient, for the most part. nfsserver - the server. It includes a DRC designed specifically for NFSv4, that is used instead of the generic DRC in sys/rpc. The build glue will be checked in later, so at this point, it consists of 3 new subdirs that should not affect kernel building. Approved by: kib (mentor)
OpenPOWER on IntegriCloud