dev_coredump_put(9)

💅 dev_coredump_put(9) 💅

okay so this is a page from the Kernel API Manual, and it's literally about cleaning up after a device has a whole meltdown. bestie, it's the cleanup crew of kernel coredumps 🧹✨

---

🌸 NAME 🌸

dev_coredump_put — remove device coredump 🗑️

Like, it yeets the coredump. That's the whole job. Iconic honestly.

---

✨ SYNOPSIS ✨

void dev_coredump_put (struct device *dev );

one function, one argument, no drama. the way that signature is just sitting there being all simple 🫶

---

🎀 ARGUMENTS 🎀

• dev — the struct device for the crashed device 💀 like yes, the one that crashed. that device's struct. the main character of this whole situation.

---

🦋 DESCRIPTION 🦋

okay so here's the tea ☕ dev_coredump_put removes the coredump, if it exists, for a given device from the file system — and it frees its associated data. and if there's no coredump? it literally does nothing. no cap. just vibes and silence 🙈

it's useful for modules that do not want to keep the coredump available after their unload. so like, if your module is heading out the door, this is how you don't leave a coredump just lying around being messy. clean exit only, periodt 💅✨

---

👑 SEE ALSO 👑

• Kernel file ./drivers/base/devcoredump.c
• dev_coredumpv(9)
• devcd_free_sgtable(9)
• devcd_read_from_sgtable(9)
• dev_coredumpm_timeout(9)
• dev_coredumpsg(9)

the whole squad fr fr, go read them too 🫶📚

---

and that's the page bestie!! 🌈 this little gem lives over in ./drivers/base, dated October 2026 — so like, she's from the future and still slaying 💜🎀 bye mwah 💋