[PATCH 0/3] mtd: rawnand: sunxi: harden protected OOB handling
James Hilliard <[email protected]>
| Newsgroups | dev.linux.lists.linux-sunxi,org.infradead.lists.linux-arm-kernel,org.infradead.lists.linux-mtd,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <20260811-sunxi-nand-protected-oob-fixes-v1-0-412e50444673@gmail.com> |
The H6/H616 variable protected-OOB implementation has three related failure cases around its per-step user-data lengths. First, propagate failures while allocating the per-step length array. Then reserve an encodable four-byte first section for the bad block marker and reject layouts which cannot provide it. Finally, replace the per-write heap allocation used for BBM compensation with the controller's bounded 32-byte stack buffer. These fixes keep the calculated, advertised and programmed OOB layouts consistent and prevent zero-sized sections from reaching the BBM path. Assisted-by: OpenAI Codex (gpt-5.6-sol, max) Signed-off-by: James Hilliard <[email protected]> --- James Hilliard (3): mtd: rawnand: sunxi: propagate user-data allocation errors mtd: rawnand: sunxi: reserve a full user-data word for BBM mtd: rawnand: sunxi: use a stack buffer for BBM randomization drivers/mtd/nand/raw/sunxi_nand.c | 32 +++++++++++++++++++++----------- 1 file changed, 21 insertions(+), 11 deletions(-) --- base-commit: 15a3cbce32994141252bb4ecfe3ff3a5d22d0b4f change-id: 20260810-sunxi-nand-protected-oob-fixes-15db4368a8ae Best regards, -- James Hilliard <[email protected]>