sbitmap_show(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ sbitmap_show β€” kernel API manual ✨

okay so bestie, you know how sbitmap_show(9) is the page? yeah. this is that. we're in the Kernel API Manual, and it's lowkey a little diagnostic icon. let's get into it πŸ’…


🌸 NAME 🌸

sbitmap_show β€” dumps the info from a &struct sbitmap straight into a &struct seq_file. that's the whole job. she's a reporter, not a hero πŸŽ€


⭐ SYNOPSIS ⭐

void sbitmap_show (struct sbitmap *sb , struct seq_file *m );

returns nothing (it's void, she's just here to say things, not to give you a value), takes your bitmap, takes your seq_file. done. periodt πŸ’–


πŸ¦‹ ARGUMENTS πŸ¦‹

  • sb β€” the bitmap to show. this is the star of the show, the main character, the thing you're dumping 🌈
  • m β€” the struct seq_file this gets written to. it's the notepad, she's the one holding the pen 🫢

πŸ‘‘ DESCRIPTION πŸ‘‘

so this whole thing is for debugging. that's the vibe check. it's not a stable public API you should build your whole lil architecture on, okay?

⚠️ heads up, bestie: the format may change at any time. no cap. so if you're parsing this output in a script and expecting it to stay the same forever… 😭 don't. it's giving "undefined behaviour but for text". it's for eyeballs, not for parsers πŸ’€

πŸ’œ SEE ALSO πŸ’œ

the whole sbitmap cinematic universe, fr fr 🧚 β€” and it lives in the kernel file ./include/linux/sbitmap.h:


and that's the page!! πŸ’« this lil beauty came out of ./include/linux and it's dated October 2026. go debug something, bestie β€” you're gonna slay πŸ”₯πŸ‘‘

πŸ“¦ where this page comes from