cifsFileInfo_put(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ cifsFileInfo_put(9) ✨

okay so this is a page from the Kernel API Manual, and it's lowkey short but like... important? it's the cleanup girlie. the one who lets go. πŸ’…


🌸 NAME 🌸

cifsFileInfo_put β€” release a reference of file priv data

like, you're done with your lil reference, so you hand it back. no hoarding bestie 🫢


✨ SYNOPSIS ✨

void cifsFileInfo_put (struct cifsFileInfo *cifs_file );

that's the whole signature, verbatim, don't @ me πŸŽ€


πŸ¦‹ ARGUMENTS πŸ¦‹

  • cifs_file β€” cifs/smb3 specific info (eg refcounts) for an open file

so basically it's the per-open-file struct holding all the cifs/smb3 flavoured details β€” refcounts and that whole situation β€” for a file that's currently open. main character struct energy fr fr πŸ‘‘


πŸ’– DESCRIPTION πŸ’–

Always potentially wait for oplock handler. See _cifsFileInfo_put.

that's it. that's the description. and the "Always" is doing a LOT of heavy lifting there β€” potentially waiting is baked into this one, unlike its underscore bestie _cifsFileInfo_put. so like, don't be surprised if it hangs out waiting on an oplock handler for a sec. it's not being flaky, it's being thorough. ✨


🧚 SEE ALSO 🧚

go read the source, iykyk πŸ’€ the real lore is in ./fs/smb/client/file.c, and the underscore twin _cifsFileInfo_put(9) is right there if you want the version that doesn't do the always-potentially-wait thing.


and that's the whole page!! short and iconic, just like some of the best manpages honestly 🌈

sign-off time: this lil gem lives under ./fs/smb/client, dated October 2026 β€” so yes, it's from the future, slay πŸ’œπŸŒΈβœ¨

πŸ“¦ where this page comes from