849  * Allocate a new open/delegation state counter. This is needed for
1073  * When we recall a delegation, we should be careful not to hand it
1077  * If a filehandle appear in either filter, a delegation is blocked.
1078  * When a delegation is recalled, the filehandle is stored in the "new"
1169 	 * delegation seqid's are never incremented.  The 4.1 special  in alloc_init_deleg()
1262  * nfs4_delegation_exists - Discover if this delegation already exists
1263  * @clp:     a pointer to the nfs4_client we're granting a delegation to
1264  * @fp:      a pointer to the nfs4_file we're granting a delegation on
1267  *      On success: true iff an existing delegation is found
1289  * hash_delegation_locked - Add a delegation to the appropriate lists
1291  * @fp:     a pointer to the nfs4_file we're granting a delegation on
1294  *      On success: NULL if the delegation was successfully hashed.
1297  *                 nfs4_client for this nfs4_file. Delegation is not hashed.
1363  * revoke_delegation - perform nfs4 delegation structure cleanup
1364  * @dp: pointer to the delegation
1367  * interface (nfsd4_revoke_states()) that's revoking a specific delegation
1381  * for removing it from the list. Inspection of where the delegation state
1734  * All nfs4 states (open, lock, delegation, layout) held by the server instance
5173  *   %true: delegation was returned
5230 		 * granting delegation.  in nfsd4_cb_recall_done()
5289 	 * we'll remove it ourself if a delegation isn't returned  in nfsd_break_deleg_cb()
5749  * It's possible that between opening the dentry and setting the delegation,
5779  * may not notice and continue using the old mode. Avoid giving out a delegation
5815 	 * Try for a write delegation first. RFC8881 section 10.4 says:  in nfs4_set_delegation()
5817 	 *  "An OPEN_DELEGATE_WRITE delegation allows the client to handle,  in nfs4_set_delegation()
5820 	 * Furthermore the client can use a write delegation for most READ  in nfs4_set_delegation()
5823 	 * Offer a write delegation in the case of a BOTH open, and ensure  in nfs4_set_delegation()
5833 	 * file for some reason, then try for a read delegation instead.  in nfs4_set_delegation()
5973  * begins each COMPOUND contains a client ID. Delegation recall can
5975  * GETATTR also holds write delegation it conflicts with.
5979  * conflicting delegation versus coming from some other client. Per
5982  * holds the conflicting delegation.
5988  * eventually revokes the delegation, which can result in loss of
6057 		dprintk("NFSD: WARNING: refusing delegation reclaim\n");  in nfs4_open_delegation()
6061 	/* 4.1 client asking for a delegation? */  in nfs4_open_delegation()
6079 	/* Otherwise the client must be confused wanting a delegation  in nfsd4_deleg_xgrade_none_ext()
6173 	* Attempt to hand out a delegation. No error return, because the  in nfsd4_process_open2()
6181 	/* 4.1 client trying to upgrade/downgrade delegation? */  in nfsd4_process_open2()
8549  * Since the lifetime of a delegation isn't limited to that of an open, a
8550  * client may quite reasonably hang on to a delegation as long as it has
8562 	 * estimates suggest that in the worst case (where every delegation  in set_max_delegations()
8563 	 * is for a different inode), a delegation could take about 1.5K,  in set_max_delegations()
8872  * delegation and a change/size GETATTR from another client. The server
8874  * attributes from the client that holds the delegation or recall the
8875  * delegation before replying to the GETATTR. See RFC 8881 section
8935 		/* Recall delegation only if client didn't respond */  in nfsd4_deleg_getattr_conflict()