STRUCT PSTORE_ZONE(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’Ύ struct pstore_zone(9) β€” the Kernel API Manual, bestie edition πŸ’Ύ

okay so picture this: you're deep in the struct pstore_zone(9) man page from the Kernel API Manual and honestly? it's giving "one little buffer, but make it official." this is the page for a single stored buffer bestie, and yes we're gonna read the whole thing together, no skipping πŸ’…


✨ NAME ✨

struct pstore_zone β€” literally just one single stored buffer πŸŽ€


🌸 SYNOPSIS 🌸

here's the whole shape of her, no cap, copy it exactly:

struct pstore_zone {
    loff_t off;
    const char *name;
    enum pstore_type_id type;
    struct psz_buffer *buffer;
    struct psz_buffer *oldbuf;
    size_t buffer_size;
    bool should_recover;
    atomic_t dirty;
 };

πŸ¦‹ MEMBERS πŸ¦‹

okay bestie, let's meet the whole cast πŸ’–

  • off β€” the zone offset of storage. like, where she sits in the storage, fr fr.
  • name β€” front-end name for this zone. that's her government name ✨
  • type β€” front-end type for this zone. her whole vibe category, iykyk.
  • buffer β€” pointer to the data buffer managed by this zone. she's literally in charge of it πŸ‘‘
  • oldbuf β€” pointer to the old data buffer. the throwback version, the archival queen πŸ™ˆ
  • buffer_size β€” bytes in buffer->data. count 'em πŸ’…
  • should_recover β€” whether this zone should recover from storage. lowkey a big deal.
  • dirty β€” whether the data in buffer dirty. (that's the original phrasing, we do not fix it, we simply report it 🫢)

⭐ Description ⭐

zone structure in memory. that's it, that's the whole description, she's short and iconic 🌈


🧚 SEE ALSO 🧚

Kernel file ./fs/pstore/zone.c β€” and then the whole friend group:


and that's the page!! source is ./fs/pstore, dated October 2026 β€” so when you cite this in your essay you say "October 2026, ./fs/pstore," slay πŸ’œβœ¨ go be a main character in the kernel, ily, bye πŸŽ€

πŸ“¦ where this page comes from