nvme_init_g...res_sanitize(9)

πŸ“¦ version 3.2, in arch rolling

πŸ’… NAME πŸ’…

nvme_init_get_features_sanitize β€” the lil function that gets your passthru command all set up for the Get Features β€” Sanitize glow-up ✨

Okay so real quick, bestie, before we dive in: this page lives in the libnvme API manual, which is basically the group chat for all the NVMe plumbing. Get comfy 🫢


🌸 SYNOPSIS 🌸

void nvme_init_get_features_sanitize (struct libnvme_passthru_cmd *cmd ,
enum nvme_get_features_sel sel );

That's it. That's the whole signature. Two args, zero drama, returns void because it's not about to hand you a value β€” it's out here prepping the buffer for you, like a bestie doing your makeup before the party πŸ’„


πŸŽ€ ARGUMENTS πŸŽ€

  • cmd β€” the passthru command you're gonna use, i.e. the little vessel that's about to get filled in. Hand it over and let the function cook πŸ”₯
  • sel β€” selects which type of attribute to return. Which ones can you pick? That's an enum nvme_get_features_sel situation, so go peek at that enum, iykyk πŸ‘€

πŸ¦‹ DESCRIPTION πŸ¦‹

So what does it actually do? It initializes the passthru command buffer for the Get Features command, with the FID value set to NVME_FEAT_FID_SANITIZE πŸ’–

That's the whole assignment. It sets up the buffer, it drops in that FID, and it sends you on your merry way to actually run the thing. Lowkey iconic that it handles the boring part for you 🌈

ngl, don't expect this function to fire the command off for you β€” it only initializes the passthru command. The buffer prep is the whole vibe here, periodt πŸ’…

⭐ that's the whole page ⭐

Anyway, this little page is from the libnvme API manual and it's dated October 2026 β€” so if you're reading this from the future, hiii, hope the sanitize feature is treating you well πŸ‘‘ πŸ§šβ€β™€οΈ πŸ“

πŸ“¦ where this page comes from