kobject_has_children(9)

📦 version 7.3.1, in nixpkgs unstable

💅 kobject_has_children — a Kernel API Manual moment (section 9, bestie)

okay so picture this: it's the Kernel API Manual, and we're doing kobject_has_children(9). yes that's the whole vibe. come on in 🎀

✨ NAME ✨

kobject_has_children — literally just tells you whether a kobject has children or not. that's it. that's the whole function. she's simple, she's iconic, she slays 💖

🦋 SYNOPSIS 🦋

bool kobject_has_children (struct kobject *kobj );

🌸 ARGUMENTS 🌸

  • kobj — the object we're testing. the one we're asking about. the main character, if you will 👑

⭐ DESCRIPTION ⭐

so basically this returns whether a kobject has other kobjects hanging around as children. like, does she have a little squad of sub-kobjects under her? yes or no, bool, done. 🫶

💀 important caveat, no cap: it does NOT account for the presence of attribute files — only sub directories. so don't come at her asking about attribute files, that's not her job, she will not answer.
🙈 also, it assumes there is no concurrent addition or removal of such children. so it relies on external locking. read that again: external locking. she is not doing the locking for you, bestie — that's on you. don't set her up like that 😭

🔥 SEE ALSO 🔥

Kernel file ./drivers/base/core.c — and like, a truly unserious number of friends. here they all are, every single one, no skips:

iykyk 💜

that's the whole page, bestie — short and sweet, one bool, one very important locking disclaimer. and before you go: this little gem lives in ./drivers/base, it's dated October 2026, and it's brought to you by the Kernel API Manual (section 9, obviously 💅). mwah, go check your locking 🎀✨🦋

📦 where this page comes from