dev_addr_del(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– dev_addr_del(9) πŸ’–

okay so bestie, welcome to dev_addr_del β€” it's a page from the Kernel API Manual and honestly it's giving "small function, big responsibility" energy. Let's get into it 🫢


✨ NAME ✨

dev_addr_del β€” release a device address πŸ’… like, let it go, it's not your address anymore.


🌸 SYNOPSIS 🌸

int dev_addr_del (struct net_device *dev , const unsigned char *addr ,
       unsigned char addr_type );

that's the whole vibe. three args, one int coming back at you ✨


πŸŽ€ ARGUMENTS πŸŽ€

  • dev β€” the device, bestie. the actual struct net_device we're messing with πŸ’»
  • addr β€” the address to delete πŸ—‘οΈ the one getting evicted, no cap
  • addr_type β€” the address type 🏷️ gotta say what kind of address it is

πŸ¦‹ DESCRIPTION πŸ¦‹

so here's the tea β˜•: dev_addr_del releases the reference to a device address and removes it from the device if the reference count drops to zero β€” like, the refcount has to hit zero before it actually gets the boot πŸ‘’. not before. the count says when. periodt.

⚠️ okay this is the important part, do NOT skip it: the caller must hold the rtnl_mutex. fr fr. that's not a suggestion, that's a lock requirement, and if you're out here calling this without it that's a you problem πŸ™ˆ

πŸ”₯ SEE ALSO πŸ”₯

okay this list is LONG and honestly kind of iconic β€” the whole friend group showed up πŸ‘‘

like I said. the whole squad 🌈


and that's the page, bestie!! πŸ§šπŸ’œ

this lil masterpiece lives in ./net/core, dated October 2026, and it's filed under dev_addr_del(9) in the Kernel API Manual β€” so when you need it again you know exactly where to look πŸ“βœ¨ go forth and release those addresses responsibly πŸ’…

πŸ“¦ where this page comes from