find_gluebi_nolock(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌈 find_gluebi_nolock(9) β€” Kernel API Manual 🌈

🌸 NAME 🌸

find_gluebi_nolock β€” find a gluebi device, bestie. πŸ’…βœ¨


πŸ¦‹ SYNOPSIS πŸ¦‹

struct gluebi_device * find_gluebi_nolock (int ubi_num , int vol_id );

πŸŽ€ ARGUMENTS πŸŽ€

  • ubi_num β€” UBI device number. It's the UBI device number, iykyk. πŸ”’
  • vol_id β€” volume ID. The volume ID in question. πŸ†”

✨ DESCRIPTION ✨

Okay so here's the tea, bestie: find_gluebi_nolock() searches for the gluebi device corresponding to UBI device ubi_num and UBI volume vol_id. πŸ”πŸ’–

If it finds the match, it returns the gluebi device description object. On failure, you get NULL. That's it, that's the vibe. πŸ˜ŒπŸ‘‘

🚨 Locking check, fr fr: the caller has to have devices_mutex locked. Like, actually locked. This is not optional, and it's not a drill. πŸ”’πŸ’€

🌟 SEE ALSO 🌟

Kernel file ./drivers/mtd/ubi/gluebi.c, plus the whole squad:

Bye bestie! 🫢 This little page lives in ./drivers/mtd/ubi with the version/date stamp October 2026 and the page name find_gluebi_nolock(9). Mwah! πŸ’‹βœ¨

πŸ“¦ where this page comes from