nlmv4 Probes

All the probes work for both synchronous and asynchronous NLMv4 procedures. The information about remote host is not available in the op-null-* probes.

Probe	args[2]
nlmv4:::op-cancel-start	nlm4_probe_cancargs_t
nlmv4:::op-cancel-done	nlm4_probe_res_t
nlmv4:::op-free-all-start	nlm4_probe_notify_t
nlmv4:::op-free-all-done	none
nlmv4:::op-lock-start	nlm4_probe_lockargs_t
nlmv4:::op-lock-done	nlm4_probe_res_t
nlmv4:::op-nm-lock-start	nlm4_probe_lockargs_t
nlmv4:::op-nm-lock-done	nlm4_probe_res_t
nlmv4:::op-null-start	none
nlmv4:::op-null-done	none
nlmv4:::op-share-start	nlm4_probe_shareargs_t
nlmv4:::op-share-done	nlm4_probe_shareres_t
nlmv4:::op-test-start	nlm4_probe_testargs_t
nlmv4:::op-test-done	nlm4_probe_testres_t
nlmv4:::op-unlock-start	nlm4_probe_unlockargs_t
nlmv4:::op-unlock-done	nlm4_probe_res_t
nlmv4:::op-unshare-start	nlm4_probe_shareargs_t
nlmv4:::op-unshare-done	nlm4_probe_shareres_t

The following table lists the probes that track the NLMv4 GRANTED callback procedure. The server notifies the client that a formerly blocked request has now been granted.

Probes	args[2]
nlmv4:::op-granted-start	nlm4_probe_testargs_t
nlmv4:::op-granted-done	nlm4_probe_res_t
nlmv4:::op-granted-res-start	nlm4_probe_testargs_t
nlmv4:::op-granted-res-done	nlm4_probe_res_t
nlmv4:::notify-granted-start	nlm4_probe_testargs_t
nlmv4:::notify-granted-done	nlm4_probe_notify_granted_res_t

When there is conflicting NFSv4 delegation, the following probe is fired:

nlmv4:::conflicting-delegation  nlm4_probe_conflicting_delegation_t