__hw_addr_ref_unsync_dev(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… __hw_addr_ref_unsync_dev(9) β€” like, the un-sync one

okay so bestie, welcome to the Kernel API Manual page for __hw_addr_ref_unsync_dev, and honestly? she's the cleanup crew of the address-syncing world. nobody throws her a parade but everybody needs her 🧹✨


🌸 NAME 🌸

__hw_addr_ref_unsync_dev β€” remove the synchronized addresses (and the references on them, yes those too) from a device, no cap


✨ SYNOPSIS ✨

void __hw_addr_ref_unsync_dev (struct netdev_hw_addr_list *list , struct
net_device *dev , int (*unsync)(struct net_device *, const unsigned char
*, int) );

like yeah, three args, one void, she's not returning anything to you, she's just done πŸ’€


πŸŽ€ ARGUMENTS πŸŽ€

  • list β€” the address list we're cleaning out. this is where the synchronized addresses (and the references on 'em) get evicted from. 🧳
  • dev β€” the device we're syncing. the whole point, the main character, the moment 🫢
  • unsync β€” a function to call if an address and the references on it should be removed. like a little callback bestie who handles the actual yeeting. πŸ”₯

πŸ¦‹ DESCRIPTION πŸ¦‹

so like. __hw_addr_ref_unsync_dev removes all the addresses that were added to the device by __hw_addr_ref_sync_dev. it's the undo button, the "never mind," the taking-your-shoes-off-at-the-door of address lists. πŸŽ€

she's intended to be called from the ndo_stop or ndo_open functions, specifically on devices that require explicit address (or references on it) add/remove notifications. those picky devices. we love them anyway. πŸ’–

πŸ‘‘ and here's the tea: if the unsync function pointer is NULL, this function can be used to just reset the sync_cnt for the addresses in the list. that's it, that's the vibe check. no callback, no removal, just a lil counter reset. 🌈

πŸ’œ SEE ALSO πŸ’œ

go read these next, iykyk β€” kernel file ./net/core/dev_addr_lists.c is where the whole squad lives:


and that's the whole page, bestie 🫢 mwah πŸ’‹ β€” this iconic little number comes to you from ./net/core, dated October 2026, and she's filed under __hw_addr_ref_unsync_dev(9) forever and ever βœ¨πŸŽ€πŸŒŸ

πŸ“¦ where this page comes from