rpmb_dev_find_device(9)

📦 version 7.3.1, in nixpkgs unstable

💅 rpmb_dev_find_device(9) — like, the whole kernel API manual vibe ✨

okay so bestie, welcome to rpmb_dev_find_device(9) — yes that's the man page name, yes it's a 9 section kernel API joint, we're in the big leagues now 🎀

🌸 NAME 🌸

rpmb_dev_find_device — returns the first matching rpmb device. literally that's the whole personality 💖

✨ SYNOPSIS ✨

struct rpmb_dev * rpmb_dev_find_device (const void *data , const struct
rpmb_dev *start , int (*match)(struct device *dev, const void *data) );

three args, one return, no drama 🌈

🦋 ARGUMENTS 🦋

  • data — the data you're handing off to the match function. it's just vibes for the matcher, ok? 🙈
  • start — the rpmb device you wanna begin with. your starting point, your main character ✨
  • match — the matching function itself. this is the whole test, the vibe check, the moment of truth 🔥

💜 DESCRIPTION 💜

so here's what happens, fr fr: it iterates over all the registered RPMB devices, and it calls match for each one, passing it the RPMB device and data 🫶

the return value of match gets checked on every single call. and if it returns anything other than 0? boom — break, and return that found RPMB device. not me getting emotional over a loop 🥹

⚠️ okay important bestie: it's the caller's responsibility to call rpmb_dev_put on the returned device when it's done with it. do not skip this. do not ghost the refcount. that's it, that's the warning 💀

⭐ RETURN ⭐

a matching rpmb device, or NULL on failure. simple as that 🍓

🧚 SEE ALSO 🧚

Kernel file ./drivers/misc/rpmb-core.c, plus the whole friend group:

okay that's the page!! shoutout to ./drivers/misc for housing all of this, and to October 2026 for the timestamp — periodt, go call rpmb_dev_put, ily, bye 💅👑

📦 where this page comes from