libnvme_sed_lock_unlock(9)

πŸ“¦ version 3.2, in arch rolling

πŸ’… libnvme_sed_lock_unlock(9) πŸ’…

okay bestie, welcome to the libnvme API manual β€” yes the whole thing, and yes we're gonna get through it together 🫢 this one's about libnvme_sed_lock_unlock, and it's literally so straightforward it's giving main character energy ✨


🌸 NAME 🌸

libnvme_sed_lock_unlock β€” change the lock state of the global range πŸ”’βœ¨

like, the global range. the whole thing. not a drill, not a section, the global one. periodt πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

int libnvme_sed_lock_unlock (struct libnvme_transport_handle *hdl ,
const struct libnvme_sed_key *key , enum libnvme_sed_lock_state state );

that's it. that's the whole vibe check. three args, one int back πŸŽ€


πŸŽ€ ARGUMENTS πŸŽ€

  • hdl β€” the transport handle πŸ’– like, your lil' connection to the drive, the main character of the plumbing. you already know her.
  • key β€” the Admin1 password πŸ”‘ ngl this one's the whole point β€” it's the credential that lets you actually do the lock thing. guard it with your life, bestie 😭
  • state β€” the new lock state πŸ‘‘ as in, what you want the lock to become. it's an enum libnvme_sed_lock_state, so check that enum for the actual values β€” iykyk 🌈

⭐ RETURN ⭐

see the return value convention above πŸ“– β€” fr fr, that's the whole note here, so peek at the convention section up top for what the int is actually telling you πŸ’€


🫢 friendly reminder: state is a enum libnvme_sed_lock_state β€” don't just vibe-guess a number, go look at the enum, bestie πŸ’œ

and that's the page!! icons only, no notes πŸ’… written under the libnvme API manual, dated October 2026 β€” mwah, go lock some stuff responsibly πŸ¦‹πŸ’–πŸŒΈ

πŸ“¦ where this page comes from