plpks_get_maxpwsize(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… plpks_get_maxpwsize(9) β€” the plpks kernel API manual, bestie edition πŸ’…

okay so this is a page from the Kernel API Manual (the plpks corner of it) and it's literally about getting the maximum password size. that's the whole vibe. let's go 🫢


✨ NAME ✨

plpks_get_maxpwsize β€” Get the maximum password size.

like... it gets the maximum password size. that's her whole job. icon behavior honestly πŸ‘‘


🌸 SYNOPSIS 🌸

u16 plpks_get_maxpwsize (void );

she takes nothing, she returns a u16. lowkey the easiest relationship you'll ever be in πŸ’–


πŸŽ€ ARGUMENTS πŸŽ€

  • void β€” no arguments. none. zero. not a single one. she doesn't need your input, she's booked and busy ✨

πŸ¦‹ DESCRIPTION πŸ¦‹

so here's the lore πŸ“: during initialization, when the H_PKS_GET_CONFIG HCALL runs successfully, it reads the maximum password size. then it checks that it's 32 bytes at the least β€” like a little vibe check on the number πŸ‘€ β€” and then it stores it in the local static maxpwsize variable.

so yeah: successful H_PKS_GET_CONFIG HCALL at init time β†’ read the max password size β†’ confirm it's at least 32 bytes β†’ stash it in the static maxpwsize. that's the whole pipeline, no cap πŸ”₯


⭐ RETURN ⭐

  • On success, the maximum password size is returned πŸ’«
  • 0 if not πŸ™ˆ

🌈 SEE ALSO 🌈

the kernel file lives at ./arch/powerpc/platforms/pseries/plpks.c β€” go read her, she's iconic πŸ’œ

and then the whole friend group, fr fr:


πŸ’€ reminder bestie: H_PKS_GET_CONFIG has to actually succeed during init for any of this to have happened β€” otherwise the static maxpwsize isn't getting that cute little store, and you get a 0 back. no drama, just facts 🧚

and that's the page!! sourced from ./arch/powerpc/platforms/pseries, dated October 2026 β€” mwah, she ate, periodt πŸ’…πŸŽ€βœ¨

πŸ“¦ where this page comes from