nfsd4_vet_deleg_time(9)

✨ nfsd4_vet_deleg_time ✨

ok so this is page nfsd4_vet_deleg_time(9) from the Kernel API Manual, and bestie it's literally the vibe-check function for delegated timestamps 💅

---

🌸 NAME 🌸

nfsd4_vet_deleg_time — the one that vets and sets the timespec when a delegated timestamp update comes through 🎀

---

🦋 SYNOPSIS 🦋

bool nfsd4_vet_deleg_time (struct timespec64 *req , const struct
timespec64 *orig , const struct timespec64 *now );

---

💖 ARGUMENTS 💖

• req — the timestamp the client sent you, fr fr 📨
• orig — the original timestamp chillin' in the inode
• now — the current time, like, right now ⏰

---

👑 DESCRIPTION 👑

okay so picture this: you get a timestamp from the client response, and this function's whole job is to cross-check it against the current timestamp in the inode and against the current time. No cap, that's it. 😌

It returns true if the inode's timestamp actually needs to be updated, and false if it doesn't. Simple. Iconic. 🫶

also — plot twist — req may also be changed if the timestamp needs to be clamped. so like, don't be surprised if it comes back a little different than it went in, bestie 🙈

---

🌈 SEE ALSO 🌈

Kernel file ./fs/nfsd/nfs4state.c — plus this whole squad of related pages:

• nfs4_delegation_exists(9)
• hash_delegation_locked(9)
• revoke_delegation(9)
• nfs4_replay_free_cache(9)
• nfsd4_revoke_states(9)
• nfsd4_revoke_export_states(9)
• nfsd_slot_shrinker_count(9)
• nfsd_slot_shrinker_scan(9)
• nfsd4_put_client(9)
• nfsd_wait_for_delegreturn(9)
• nfsd_breaker_owns_lease(9)
• nfsd4_deleg_lm_open_conflict(9)
• nfsd4_process_open2(9)
• nfsd4_force_end_grace(9)
• nfs4_preprocess_stateid_op(9)
• nfs4_preprocess_seqid_op(9)
• nfsd4_release_lockowner(9)
• nfsd4_deleg_getattr_conflict(9)
• nfsd_get_dir_deleg(9)
• nfsd_update_cmtime_attr(9)

---

💀 reminder: this page lives under ./fs/nfsd and it's stamped October 2026. yes, the future. we stay ahead 💅

and that's the whole page, bestie — go forth and vet those timestamps 🧚✨🍓