STRUCT PSTORE_BLK_CONFIG(9)

✨ struct pstore_blk_config(9) ✨

okay bestie, so this is a page out of the Kernel API Manual, section 9 — we're looking at struct pstore_blk_config, and honestly? it's giving "the pstore_blk backend configuration" and nothing less 💅

🌸 NAME 🌸

struct pstore_blk_config — literally the configuration for the pstore_blk backend. that's the whole vibe. 🎀

🦋 SYNOPSIS 🦋

here's the whole struct, copy-paste energy, no cap:

struct pstore_blk_config {
    char device[80];
    enum kmsg_dump_reason max_reason;
    unsigned long kmsg_size;
    unsigned long pmsg_size;
    unsigned long console_size;
    unsigned long ftrace_size;
 };

👑 Members 👑

okay now the members, one by one, main character energy each:

• device — the name of the desired block device. like, which block device do you want, bestie. it's a char[80], so plenty of room for the name 🫶
• max_reason — the maximum kmsg dump reason to store to the block device. an enum kmsg_dump_reason, so it's got opinions.
• kmsg_size — total size for kmsg dumps. unsigned long, naturally.
• pmsg_size — total size of the pmsg storage area. yes, unsigned long too, they're all matching, it's a coordinated outfit 💜
• console_size — total size of the console storage area. that's the size, of the console storage area. iconic.
• ftrace_size — total size for ftrace logging data, and listen — for all CPUs. not one, all of them. 🔥

🌈 SEE ALSO 🌈

• the kernel file ./include/linux/pstore_blk.h — go read it, iykyk 📖
• struct pstore_device_info(9)
• pstore_blk_get_config(9)

fr fr though, if you're poking at the block-device side of pstore, these three are your group chat. don't leave them on read. 😭

so yeah, that's the whole thing — struct's from ./include/linux, dated October 2026, and that's the tea 💖 stay slay, keep your sizes unsigned long, and go read your headers 🧚‍♀️🌸