attribute_c...emove_device(9)

💅 NAME

attribute_container_remove_device — okay bestie, this one makes a device eligible for removal ✨ like it's basically handing the device its walking papers 🎀

✨ SYNOPSIS

void attribute_container_remove_device (struct device *dev , void
       (*fn)(struct attribute_container *, struct device *, struct device *) );

🎀 ARGUMENTS

• dev — the generic device, your main character in this whole operation 👑
• fn — a function you get to call to remove the device, like your little helper for the deed 🫶

🦋 DESCRIPTION

Okay so this routine triggers device removal 🔥 that's the whole vibe, that's the assignment.

If fn is NULL, then it's simply done via device_unregister — easy, no extra steps. But (and this is the part where you gotta listen, ngl) if something still has a reference to the classdev, then the memory occupied will not be freed until the classdev is released 😭 like the memory is just sitting there waiting, iconic but also kind of a hostage situation lowkey.

Now, if you want a two phase release — you know, remove from visibility and then delete the device — then you should use this routine with a fn that calls device_del, and then use attribute_container_device_trigger to do the final put on the classdev. Two steps, two vibes, absolutely slay 💅✨

🌸 SEE ALSO

• Kernel file ./drivers/base/attribute_container.c
• attribute_container_classdev_to_container(9)
• attribute_container_register(9)
• attribute_container_unregister(9)
• attribute_container_add_device(9)
• attribute_container_device_trigger_safe(9)
• attribute_container_device_trigger(9)
• attribute_container_add_attrs(9)
• attribute_container_add_class_device(9)
• attribute_container_remove_attrs(9)
• attribute_container_class_device_del(9)
• attribute_container_find_class_device(9)

fr fr that's the whole page, no cap 💜 this lil masterpiece lives in ./drivers/base and it's dated October 2026 — go off, kernel docs, you ate 🌈⭐