nand_region_is_secured(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… nand_region_is_secured(9) πŸ’…

okay so bestie, welcome to the Kernel API Manual, section 9 β€” yes, that section 9, the kernel one, not the "read the fine print" one 😭 this is the page for nand_region_is_secured, and honestly? it's a little baddie with one job and it does it slayfully πŸ’–


✨ NAME ✨

nand_region_is_secured β€” literally just checks if a region is secured πŸŽ€ that's it, that's the whole vibe check


πŸ¦‹ SYNOPSIS πŸ¦‹

bool nand_region_is_secured (struct nand_chip *chip , loff_t offset ,
u64 size );

look at her go. returns a bool, takes three args, no cap πŸ’…


🌸 ARGUMENTS 🌸

  • chip β€” the NAND chip object 🧚 like, the actual chip you're asking about
  • offset β€” offset of the region you wanna check πŸ“
  • size β€” size of the region you wanna check πŸ“

πŸ’œ DESCRIPTION πŸ’œ

so what does she do? she checks if the region is secured by comparing the offset and size you handed her against the list of secure regions obtained from DT πŸ‘‘ (device tree, iykyk).

returns true if the region is secured πŸ’– else false 🫢

that's the whole flow. no drama, no side quests, just a clean little comparison and a boolean. iconic behavior honestly ✨


πŸ”₯ SEE ALSO πŸ”₯

the girlies she hangs out with πŸ’… all of these are from the kernel file ./drivers/mtd/nand/raw/nand_base.c β€” go say hi:


πŸ’€ real talk: this page lives in ./drivers/mtd/nand/raw β€” that's the source path, that's her address, don't @ me.

okay that's the whole page bestie, go forth and check your regions πŸ¦‹βœ¨πŸ’–

β€” xoxo, signed off October 2026 🌈 from the ./drivers/mtd/nand/raw girlies, mwah πŸ’…πŸŽ€

πŸ“¦ where this page comes from