Cross Reference: /illumos-gate/usr/src/uts/common/fs/nfs/nfs4

Lines Matching refs:locks
1973 			 * (in the absence of locks).
2267 		 * We could attempt to clean up locks, except we're sure
2268 		 * that the current process didn't acquire any locks on
2287 	 * release all of the SYSV style record locks.  Otherwise,
2289 	 * of the network locks.  All of the locks held by this
10517 	 * Don't allow concurrent locks and mapping if mandatory locking is
10924 	 * locks, this is so that the process gets the latest bits from the
10928 	 * allow unlocks to succeed, to avoid having orphan locks on the
11903  * structure without requiring any other locks.
12007  * structure without requiring any other locks.
12579 		 * NFS client can't store remote locks itself
13377 		 * No lock owner so no locks to unlock.
13798 			 * We do not register lost locks locally in
13997 		 * with what the application thinks it has for locks.
14002 		 * the locks that are held.
14134  * Client locks are registerred locally by oring the sysid with
14135  * LM_SYSID_CLIENT. The server registers locks locally using just the sysid.
14347 	 * if get error NFS4ERR_DENIED (for blocking locks) or NFS4ERR_GRACE.
14539 	 * If the file is already mapped and there are locks, then they
14540 	 * should be all safe locks.  So adding or removing a lock is safe
14574  * recording locks locally.
14576  * This should handle conflicts/cooperation with NFS v2/v3 since all locks
14630  * Release any locks on the given vnode that are held by the current
14682 	 * locks on the file.  (In theory we shouldn't have to make this
14702 	    "nfs4_lockrelease: possible orphan %d, remote locks %d, for "
14718 			 * local locks before we continue.
15744  * See if these two locks overlap, and if so return 1;
15779 	    "locks intersect"));
15799 	 * intersections of locks registered by the client with the local host
15846  * If we are unable to fix up the locks, we send SIGLOST to the affected
15855 	locklist_t *locks, *llp, *ri_llp, *tmp_llp;
15865 	 * Find active locks for this vp from the local locking code.
15866 	 * Scan through this list and find out the locks that intersect with
15871 	 * region locks are added to ri_llp in increasing l_start order.
15875 	locks = flk_active_locks_for_vp(vp);
15878 	for (llp = locks; llp != NULL; llp = llp->ll_next) {
15881 		 * Pick locks that belong to this pid/lockowner
15891 	 * the locks that were/are active before the server replied to the
15892 	 * last/lost lock. Issue these locks to the server here. Playing these
15893 	 * locks to the server will re-establish aur current local locking state
15921 	 * lock does not overlap with the locks in the ri_llp but are locked
15953 	 * In the case where the lost lock ends after all intersecting locks,
15974 	if (locks != NULL)
15975 		flk_free_locklist(locks);