ENUM COREDUMP_MARK(9)

💖 NAME

enum coredump_mark — the little markers for the coredump socket, bestie ✨

🌸 SYNOPSIS

Okay so picture this enum, right? Here's exactly what it looks like:

enum coredump_mark {
    COREDUMP_MARK_REQACK ,
    COREDUMP_MARK_MINSIZE ,
    COREDUMP_MARK_MAXSIZE ,
    COREDUMP_MARK_UNSUPPORTED ,
    COREDUMP_MARK_CONFLICTING ,
    __COREDUMP_MARK_MAX

};

🎀 Constants

These are the glow-up values, no cap 💅:

• COREDUMP_MARK_REQACK — the coredump request and ack was successful 🎉 iconic behaviour honestly
• COREDUMP_MARK_MINSIZE — the provided coredump_ack size was too small 😭 tiny. too tiny.
• COREDUMP_MARK_MAXSIZE — the provided coredump_ack size was too big 💀 like girl, that's way too much
• COREDUMP_MARK_UNSUPPORTED — the provided coredump_ack mask was invalid 🙈 not it
• COREDUMP_MARK_CONFLICTING — the provided coredump_ack mask has conflicting options 😵‍💫 they're fighting fr fr
• __COREDUMP_MARK_MAX — the maximum coredump mark value 👑 the ceiling, the limit, the final boss

🦋 Description

So here's the vibe: the kernel will place a single byte on the coredump socket. That's it — one byte, main character energy 🌟. And the markers? They notify userspace whether the coredump ack succeeded or failed. Slay. Simple, useful, lowkey essential 🫶

🌈 SEE ALSO

• Kernel file ./tools/include/uapi/linux/coredump.h struct coredump_req(9), struct coredump_ack(9) 🦋

And that's the whole page, bestie 💜 — brought to you by ./tools/include/uapi/linux, dated October 2026, and honestly? Periodt. 💅🎀