nfsd4_encode..._attr_change(9)

📦 version 7.3.1, in nixpkgs unstable

💅 NAME 💅

nfsd4_encode_dir_attr_change — bestie, the original literally leaves this one blank (no cap, there's just a dash and then 🦗 crickets), so we're all just vibing with the function name and the synopsis below. It's giving mysterious. It's giving "read the next section."

This page lives in the Kernel API Manual ✨ (the manual name is nfsd4_encode..._attr_change(9), yes with the lil dots, that's not a typo, that's just how she's listed 👑).

🌸 SYNOPSIS 🌸

u8 * nfsd4_encode_dir_attr_change (struct xdr_stream *xdr , struct
nfs4_delegation *dp , struct nfsd_file *nf );

Three args, one return pointer, let's go 🎀

🦋 ARGUMENTS 🦋

  • xdr — the stream we're encoding the fattr4 into. This is where the bytes go, periodt ✨
  • dp — the delegation where the event actually happened 💫
  • nf — the nfsd_file that's opened on the directory 🗂️

💖 DESCRIPTION 💖

Okay so literally all this does: encode a dir attr change event. That's it. That's the whole job. Short and iconic, lowkey the most efficient description on the whole system 🫶

🔥 RETURN 🔥

Three possible outcomes, and you gotta know which is which, iykyk:

  • A pointer to the start of the encoded event on success — slay, we ate 💅
  • NULL if there were no requested attributes to report — in that case the caller should omit the event entirely 🙈
  • An ERR_PTR if the event was requested but could not be marshalled into xdr — and in that case the caller should recall the delegation 😭 (yes, that's the dramatic one, don't ignore it)
bestie pls actually check which of the three you got, because "omit the event" and "recall the delegation" are very different vibes 💀

🌈 SEE ALSO 🌈

⭐ and that's the page!! source is ./fs/nfsd, dated October 2026 — go off, kernel docs, we'll see you in the future 🧚‍♀️💜

📦 where this page comes from