lsm_plugin_info_get(3)

πŸ“¦
version 1.10.3 Β· 3 versions
, in fedora 43, fedora 44

✨ lsm_plugin_info_get ✨

okay bestie, welcome to the lsm_plugin_info_get(3) page, straight outta the Libstoragemgmt C API Manual πŸ’– this one's a lil function that spills the tea on your plug-in. let's get into it 🫢


🌸 NAME 🌸

lsm_plugin_info_get β€” retrieves information about the plug-in πŸ‘‘

πŸŽ€ SYNOPSIS πŸŽ€

int lsm_plugin_info_get (lsm_connect *conn, char **desc, char **version,
lsm_flag flags);

πŸ¦‹ ARGUMENTS πŸ¦‹

  • conn β€” a valid lsm_connect pointer. gotta be the real deal, no fake ones πŸ’…
  • desc β€” plug-in version. yes, the page really does say "version" here, i'm just the messenger 😭 the returned string should be freed manually with the free library call. like, you own that string now, bestie, it's your responsibility 🫢
  • version β€” plug-in version. and the returned string should be freed manually too. don't let it leak, that's not the vibe 🌸
  • flags β€” reserved for future use, must be LSM_CLIENT_FLAG_RSVD. no freestyling here, it's literally the only acceptable value πŸ™ˆ

⭐ VERSION ⭐

1.0

πŸ’œ DESCRIPTION πŸ’œ

retrieves information about the plug-in. that's it, that's the whole job. iconic, honestly πŸ‘‘

πŸ”₯ RETURN πŸ”₯

it hands you back an error code, as enumerated by lsm_error_number:

  • LSM_ERR_OK β€” on success. slay, we ate πŸ’…βœ¨
  • LSM_ERR_INVALID_ARGUMENT β€” when any argument is NULL, or it's not a valid lsm_connect pointer, or the flags are invalid. basically when the vibe check fails πŸ’€

lowkey important: that desc and version memory is yours to free. the function does not do it for you, no cap 🧚

and that's the whole page bestie, go forth and retrieve plug-in info responsibly πŸŒˆπŸ“

signing off from the February 2026 edition of lsm_plugin_info_get, page lsm_plugin_info_get(3) β€” mwah, ily, bye πŸ’–πŸŽ€

πŸ“¦ where this page comes from