smb2_populate_readdir_entry(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… smb2_populate_readdir_entry(9)

okay so bestie, welcome to the Kernel API Manual page for smb2_populate_readdir_entry(9) ✨ we are absolutely gonna get this directory-entry encoding situation understood, no cap 🫢


πŸŽ€ NAME πŸŽ€

smb2_populate_readdir_entry β€” encodes a directory entry in the smb2 response buffer πŸ’–

✨ SYNOPSIS ✨

here’s the signature exactly as it is, because we do not mess with code vibes πŸ’…

int smb2_populate_readdir_entry (struct ksmbd_conn *conn , int
info_level , struct ksmbd_dir_info *d_info , struct ksmbd_kstat
*ksmbd_kstat );

🌸 ARGUMENTS 🌸

  • conn β€” the connection instance, aka the whole connection situation 🫢
  • info_level β€” the smb information level
  • d_info β€” the structure that includes variables for query dir πŸ‘€
  • ksmbd_kstat β€” ksmbd’s wrapper of dirent stat information ✨

πŸ¦‹ DESCRIPTION πŸ¦‹

so here’s the tea: if a directory has many entries, find first can’t read it fully 😭. find next might be called multiple times to read the remaining dir entries. that’s the whole plot, bestie πŸ’€

πŸ’… RETURN πŸ’…

0 on success, otherwise error. that’s it, periodt πŸ”₯

πŸ‘‘ SEE ALSO πŸ‘‘

if you’re going down the rabbit hole, these are the neighbors πŸ‘€ β€” the kernel file is ./fs/smb/server/smb2pdu.c, and the whole squad is:


🌸 sign-off bestie: source ./fs/smb/server, date October 2026, page smb2_populate_readdir_entry(9) β€” mwah πŸ’‹βœ¨

πŸ“¦ where this page comes from