dev_coredumpsg(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ dev_coredumpsg(9) ✨

okay bestie, welcome to the Kernel API Manual, section 9 β€” yes, the kernel docs can be cute too πŸ’… This one is all about dev_coredumpsg, and it's giving "device coredump but make it scatterlist" energy 🌸


🌟 NAME 🌟

dev_coredumpsg β€” create a device coredump that uses a scatterlist as its data parameter πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

void dev_coredumpsg (struct device *dev , struct scatterlist *table ,
       size_t datalen , gfp_t gfp );

πŸ’– ARGUMENTS πŸ’–

  • dev β€” the struct device for the crashed device 😭 like, the device that had a whole moment and needs its coredump collected.
  • table β€” the dump data πŸ“¦ yes, the actual data, living in a scatterlist.
  • datalen β€” length of the data πŸ“ exactly how much data we're working with.
  • gfp β€” allocation flags 🧚 the flags used when allocating, bestie.

πŸ”₯ DESCRIPTION πŸ”₯

This makes a brand-new device coredump for the device you passed in ✨

Here's the tea: if a previous coredump hasn't been read yet, the new coredump gets discarded. no cap, it just gets thrown away πŸ™ˆ

The data's lifetime is handled by the device coredump framework β€” it's the main character here πŸ‘‘ β€” and when the data is no longer needed, the framework will free it. so you don't have to do the cleanup yourself, periodt πŸ’œ


🌈 SEE ALSO 🌈


and that's the whole vibe, bestie 🫢 this page lives under ./drivers/base and it's dated October 2026 β€” iconic, honestly β­πŸ’–

πŸ“¦ where this page comes from