binder_inc_ref_olocked(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay bestie, welcome to binder_inc_ref_olocked(9) from the Kernel API Manual β€” this is the page about incrementing the ref for given handle πŸ’…βœ¨

πŸ’– NAME πŸ’–

binder_inc_ref_olocked β€” increment the ref for given handle. That's the assignment, and it ate. πŸ’–

✨ SYNOPSIS ✨

int binder_inc_ref_olocked (struct binder_ref *ref , int strong , struct list_head *target_list );

πŸŽ€ ARGUMENTS πŸŽ€

okay so here's the cast, bestie:

  • ref β€” the ref that's getting incremented. Main character of this call, honestly. 🫢
  • strong β€” if this is true, you're doing a strong increment; otherwise it's a weak one. Binary queen. πŸ’…
  • target_list β€” the list you queue node work on. Drop the node work there. πŸŽ€

πŸ¦‹ DESCRIPTION πŸ¦‹

Increment the ref. That's the move. But the lock vibe check is real: ref->proc->outer_lock must be held on entry.

⚠️ no cap: ref->proc->outer_lock must be held on entry. Like, held before you call this, bestie. Don't skip the lock. 😭

🌸 RETURN 🌸

It returns 0 if successful, else errno. So 0 is the slay outcome; anything else is the errno situation. ✨

πŸ”₯ SEE ALSO πŸ”₯

Kernel file: ./drivers/android/binder.c β€” and here's the whole related-besties lineup, no skips:

mwah πŸ’‹ β€” source/version: ./drivers/android; date: October 2026.

πŸ“¦ where this page comes from