devlink_rel_...ed_in_notify(9)

🦋 NAME 🦋

ok so bestie, welcome to devlink_rel_nested_in_notify(9) — the little function whose whole job is to notify the object that this devlink instance is nested in 🫶

(it's in section 9 of the Kernel API Manual, iykyk 💅)

---

✨ SYNOPSIS ✨

void devlink_rel_nested_in_notify (struct devlink *devlink );

that's it. that's the whole signature. no return value, she just does things 💅

---

🎀 ARGUMENTS 🎀

• devlink — a devlink. that's literally the description, that's all the docs give us, and honestly? iconic minimalism ✨ it's the devlink instance you're working with, periodt.

---

🌸 DESCRIPTION 🌸

so here's the vibe check: this gets called when a devlink instance's network namespace changes 🔥

and if this devlink instance happens to be nested in another devlink object, then a notification about a change of that object should be sent over netlink. that's the whole point of her being here 💖

now the tricky part, and no cap this matters — the parent devlink instance lock needs to be taken during the notification preparation. but here's the thing: the parent may or may not be locked 😭 so we can't just grab it and go. that's exactly why 'work' is utilized — it handles the may-or-may-not-be-locked situation for us 🧚

lowkey the whole design is "we don't know if the parent lock is held, so we defer it" and honestly? she ate. 🍓

---

👑 SEE ALSO 👑

• Kernel file ./net/devlink/core.c
• devlink_try_get(9)
• devl_register(9)
• devl_unregister(9)
• devlink_alloc_ns(9)
• devlink_free(9)

all the devlink besties in one place, go read them, they're literally so good 🌈⭐

---

ok that's the whole page, mwah 💋 — this one comes to you from ./net/devlink, dated October 2026, and it's genuinely one of the cutest little kernel API pages out there. go forth and notify your nested objects, bestie 🎀💜