From: sashiko-bot@kernel.org
To: "Gabor Juhos" <j4g8y7@gmail.com>, "Mark Brown" <broonie@kernel.org>
Cc: "Md Sadre Alam" <md.alam@oss.qualcomm.com>,
"Sricharan Ramabadhran" <quic_srichara@quicinc.com>,
"Varadarajan Narayanan" <varadarajan.narayanan@oss.qualcomm.com>,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH 1/7] spi: spi-qpic-snand: use the common qcom_nandc_check_flash_errors() function
Date: Tue, 10 Nov 2026 23:16:28 +0000 [thread overview]
Message-ID: <sashiko-outbox-207871@kernel.org> (raw)
In-Reply-To: <20261109-qpic-snand-use-common-functions-v1-1-1e8601e2db84@gmail.com>
Thank you for your contribution! Sashiko AI review found no new issues
in this patch, but noticed 1 related pre-existing issue it does not
introduce:
- [Medium] spi: spi-qpic: OOB data corruption in qcom_spi_read_last_cw()
[1]
--
commit e9db2cf0f483f41efa5a2350f20a79b1f0a4fe75
Author: Gabor Juhos <j4g8y7@gmail.com>
spi: spi-qpic-snand: use the common qcom_nandc_check_flash_errors() function
This commit replaces the local qcom_spi_check_raw_flash_errors() helper
with the common qcom_nandc_check_flash_errors() function from qpic_common.
> diff --git a/drivers/spi/spi-qpic-snand.c b/drivers/spi/spi-qpic-snand.c
> index 41685a286e381..981e16221b59e 100644
> --- a/drivers/spi/spi-qpic-snand.c
> +++ b/drivers/spi/spi-qpic-snand.c
[ ... ]
> @@ -651,7 +635,7 @@ static int qcom_spi_read_last_cw(struct qcom_nand_controller *snandc,
> return ret;
> }
>
> - ret = qcom_spi_check_raw_flash_errors(snandc, 1);
> + ret = qcom_nandc_check_flash_errors(snandc, 1);
> if (ret)
> return ret;
[Severity: Medium]
This problem wasn't introduced by this patch, but can qcom_spi_read_last_cw()
return corrupted OOB data [1] when a raw OOB read spans beyond the bad
block marker?
qcom_spi_read_page() routes all raw OOB-only reads (snandc->qspi->oob_rw &&
snandc->qspi->raw_rw) to qcom_spi_read_last_cw():
drivers/spi/spi-qpic-snand.c:qcom_spi_read_page() {
...
if (snandc->qspi->oob_rw && snandc->qspi->raw_rw)
return qcom_spi_read_last_cw(snandc, op);
...
}
However, qcom_spi_read_last_cw() only reads the final codeword into
snandc->data_buffer and copies op->data.nbytes starting from bbpos:
drivers/spi/spi-qpic-snand.c:qcom_spi_read_last_cw() {
...
bbpos = mtd->writesize - ecc_cfg->cw_size * (num_cw - 1);
...
memcpy(op->data.buf.in, snandc->data_buffer + bbpos, op->data.nbytes);
}
Because physical OOB bytes are distributed across all codewords in a
multi-codeword page, a full raw OOB read (such as via nanddump -n --oob)
misses the OOB data from earlier codewords and returns shifted data from
the final codeword instead.
[1] https://sashiko.dev/#/bug/linux-d2e2b583-de83-4f91-a87f-a7c888dd45c9
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261109-qpic-snand-use-common-functions-v1-0-1e8601e2db84@gmail.com?part=1
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2026-11-10 23:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 19:41 [PATCH 0/7] spi: spi-qpic-snand: use generic code from the 'qpic_common' module Gabor Juhos
2026-11-09 19:41 ` [PATCH 1/7] spi: spi-qpic-snand: use the common qcom_nandc_check_flash_errors() function Gabor Juhos
2026-11-10 23:16 ` sashiko-bot [this message]
2026-11-09 19:41 ` [PATCH 2/7] spi: spi-qpic-snand: use the common qcom_nandc_config_page_read() function Gabor Juhos
2026-11-10 23:20 ` sashiko-bot
2026-11-09 19:41 ` [PATCH 3/7] spi: spi-qpic-snand: use the common qcom_nandc_config_page_write() function Gabor Juhos
2026-11-10 23:24 ` sashiko-bot
2026-11-09 19:41 ` [PATCH 4/7] spi: spi-qpic-snand: use the common qcom_nandc_config_cw_write() function Gabor Juhos
2026-11-09 19:45 ` sashiko-bot
2026-11-09 19:41 ` [PATCH 5/7] spi: spi-qpic-snand: use the common qcom_nandc_set_read_loc_first() function Gabor Juhos
2026-11-09 19:41 ` [PATCH 6/7] spi: spi-qpic-snand: use the common qcom_nandc_set_read_loc_last() function Gabor Juhos
2026-11-09 19:41 ` [PATCH 7/7] spi: spi-qpic-snand: use the common 'qcom_nandc_read_stats' structure Gabor Juhos
2026-11-10 18:46 ` [PATCH 0/7] spi: spi-qpic-snand: use generic code from the 'qpic_common' module Mark Brown
2026-11-10 21:18 ` Gabor Juhos
2026-11-10 23:50 ` Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=sashiko-outbox-207871@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=broonie@kernel.org \
--cc=j4g8y7@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=md.alam@oss.qualcomm.com \
--cc=quic_srichara@quicinc.com \
--cc=sashiko-reviews@lists.linux.dev \
--cc=varadarajan.narayanan@oss.qualcomm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox