diff options
| author | Mark Brown <broonie@kernel.org> | 2026-09-17 16:24:31 +0100 |
|---|---|---|
| committer | Mark Brown <broonie@kernel.org> | 2026-09-17 16:24:31 +0100 |
| commit | ca01ebd9e2ed0ea7ed4a068bcd666b0f394581ac (patch) | |
| tree | 4e01c4d37fda32cec54c2e30f734feeb0ad41068 /tools/perf/scripts/python | |
| parent | 333c6f61629bff9921813208f1a92f9ba845abdd (diff) | |
| parent | 8d691164547832f43289a7d5f3450738ead98c2d (diff) | |
spi: spi-qpic-snand: fix the stale ECC context pointer
Johan Alvarado <contact@c127.dev> says:
qcom_spi_ecc_init_ctx_pipelined() installs the ooblayout but never
publishes the ECC context it allocates, so qcom_spi_ooblayout_ecc() and
qcom_spi_ooblayout_free() run against a pointer that describes something
else - a zeroed struct on a first probe, the previous attempt's freed
context on a retry. On IPQ5018 the qcom,smem-part parser makes that retry
routine, and like half the boots on a Mercusys MR80X failed to mount the
rootfs.
Patch 1 is the fix and is unchanged from v1. Patch 2 removes what becomes
redundant once the context is published. It is a cleanup with no
functional change, so it carries no Fixes: tag and is not marked for
stable.
Patch 1 was applied to mtd/fixes as 93bc7c4d2f41 on 2026-09-04 and
dropped the same day, so nothing from this series is queued.
Link: https://patch.msgid.link/20260911184416.109790-1-contact@c127.dev
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions
