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 3/7] spi: spi-qpic-snand: use the common qcom_nandc_config_page_write() function
Date: Tue, 10 Nov 2026 23:24:04 +0000 [thread overview]
Message-ID: <sashiko-outbox-207894@kernel.org> (raw)
In-Reply-To: <20261109-qpic-snand-use-common-functions-v1-3-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:
- [Critical] spi: qpic-snand: OOB data ignored during combined data and
OOB operations [1]
--
commit 62e1a50299465a13da198b1f4ac1536c497b8877
Author: Gabor Juhos <j4g8y7@gmail.com>
spi: spi-qpic-snand: use the common qcom_nandc_config_page_write() function
This commit replaces the local qcom_spi_config_page_write() helper with the
common qcom_nandc_config_page_write() function from the qpic_common module.
> diff --git a/drivers/spi/spi-qpic-snand.c b/drivers/spi/spi-qpic-snand.c
> index cf75c142303f8..a825bdb93a8a1 100644
> --- a/drivers/spi/spi-qpic-snand.c
> +++ b/drivers/spi/spi-qpic-snand.c
[ ... ]
> @@ -1194,7 +1188,7 @@ static int qcom_spi_program_ecc(struct qcom_nand_controller *snandc,
> snandc->regs->ecc_bch_cfg = cpu_to_le32(ecc_bch_cfg);
> snandc->regs->exec = cpu_to_le32(1);
>
> - qcom_spi_config_page_write(snandc);
> + qcom_nandc_config_page_write(snandc);
[Severity: Critical]
This problem wasn't introduced by this patch, but does qcom_spi_program_ecc()
and qcom_spi_read_page_ecc() ignore the caller-supplied OOB data during
combined page and OOB operations [1]?
When the spinand framework performs a combined operation via
spinand_write_page() or spinand_read_page(), op->data.buf points to a single
contiguous buffer containing both the page data and OOB data. However, both
functions hardcode oob_buf to the internal snandc->qspi->oob_buf without
copying the caller's OOB payload in from op->data.buf.out + mtd->writesize on
writes, or copying the read OOB data back out to op->data.buf.in +
mtd->writesize on reads:
drivers/spi/spi-qpic-snand.c:qcom_spi_program_ecc() {
...
if (snandc->qspi->data_buf)
data_buf = snandc->qspi->data_buf;
oob_buf = snandc->qspi->oob_buf;
...
}
As a result, combined reads return stale or uninitialized OOB bytes to the
caller, and combined writes silently program garbage into the flash OOB area.
[1] https://sashiko.dev/#/bug/linux-7dd8ed16-d251-4477-8c16-a5a7a68cc6e1
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261109-qpic-snand-use-common-functions-v1-0-1e8601e2db84@gmail.com?part=3
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2026-11-10 23:24 UTC|newest]
Thread overview: 26+ 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 ` 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-09 19:41 ` Gabor Juhos
2026-11-10 23:16 ` sashiko-bot
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-09 19:41 ` 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-09 19:41 ` Gabor Juhos
2026-11-10 23:24 ` sashiko-bot [this message]
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:41 ` 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 ` 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 ` 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-09 19:41 ` 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 18:46 ` Mark Brown
2026-11-10 21:18 ` Gabor Juhos
2026-11-10 21:18 ` Gabor Juhos
2026-11-10 23:50 ` Mark Brown
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-207894@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.