From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Manivannan Sadhasivam <mani@kernel.org>
Cc: Md Sadre Alam <quic_mdalam@quicinc.com>,
Sricharan Ramabadhran <quic_srichara@quicinc.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Tudor Ambarus <tudor.ambarus@linaro.org>,
Pratyush Yadav <pratyush@kernel.org>,
Michael Walle <michael@walle.cc>,
linux-mtd@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH 8/8] mtd: rawnand: qcom: Fix address parsing within ->exec_op()
Date: Thu, 27 Jul 2023 16:59:23 +0200 [thread overview]
Message-ID: <20230727165923.32488041@xps-13> (raw)
In-Reply-To: <20230717063843.GA7062@thinkpad>
Hi Sadre,
mani@kernel.org wrote on Mon, 17 Jul 2023 12:08:43 +0530:
> On Sun, Jul 16, 2023 at 04:46:12PM +0200, Miquel Raynal wrote:
> > The naddrs variable is initialized but not used. Fixing this could have
> > been a matter of dropping the variable, but the right way to do it looks
> > a bit more complex: we can avoid useless writes to the q_op structure by
> > using it. In practice we could even have possible out-of-bound bugs with
> > the existing implementation. Let's fix all that by just performing the
> > right number of assignments in the addr{1,2}_reg fields.
> >
> > Fixes: 89550beb098e ("mtd: rawnand: qcom: Implement exec_op()")
> > Reported-by: kernel test robot <lkp@intel.com>
> > Closes: https://lore.kernel.org/oe-kbuild-all/202307131959.PdPSC86K-lkp@intel.com/
> > Closes: https://lore.kernel.org/oe-kbuild-all/202307131730.NOYbcjBr-lkp@intel.com/
> > Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
>
> LGTM! But I'm relying on Sadre to test it.
>
> Acked-by: Manivannan Sadhasivam <mani@kernel.org>
I don't think I've received feedback from Sadre, I would like to close
these issues, can you please test and give us feedback?
Thanks a lot,
Miquèl
>
> - Mani
>
> > ---
> > drivers/mtd/nand/raw/qcom_nandc.c | 13 +++++++------
> > 1 file changed, 7 insertions(+), 6 deletions(-)
> >
> > diff --git a/drivers/mtd/nand/raw/qcom_nandc.c b/drivers/mtd/nand/raw/qcom_nandc.c
> > index 4fc8dafa8f03..dc8ca60fc2e2 100644
> > --- a/drivers/mtd/nand/raw/qcom_nandc.c
> > +++ b/drivers/mtd/nand/raw/qcom_nandc.c
> > @@ -2616,12 +2616,13 @@ static void qcom_parse_instructions(struct nand_chip *chip,
> > offset = nand_subop_get_addr_start_off(subop, op_id);
> > naddrs = nand_subop_get_num_addr_cyc(subop, op_id);
> > addrs = &instr->ctx.addr.addrs[offset];
> > - for (i = 0; i < MAX_ADDRESS_CYCLE; i++) {
> > - if (i < 4)
> > - q_op->addr1_reg |= (u32)addrs[i] << i * 8;
> > - else
> > - q_op->addr2_reg |= addrs[i];
> > - }
> > +
> > + for (i = 0; i < min_t(unsigned int, 4, naddrs); i++)
> > + q_op->addr1_reg |= addrs[i] << (i * 8);
> > +
> > + if (naddrs > 4)
> > + q_op->addr2_reg |= addrs[4];
> > +
> > q_op->rdy_delay_ns = instr->delay_ns;
> > break;
> >
> > --
> > 2.34.1
> >
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-07-27 15:00 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-16 14:46 [PATCH 0/8] mtd: rawnand: qcom: Misc fixes Miquel Raynal
2023-07-16 14:46 ` [PATCH 1/8] mtd: rawnand: qcom: Use the BIT() macro Miquel Raynal
2023-07-17 2:25 ` Manivannan Sadhasivam
2023-07-28 2:16 ` Tudor Ambarus
2023-07-28 12:35 ` Miquel Raynal
2023-07-16 14:46 ` [PATCH 2/8] mtd: rawnand: qcom: Use u8 instead of uint8_t Miquel Raynal
2023-07-17 2:26 ` Manivannan Sadhasivam
2023-07-28 2:17 ` Tudor Ambarus
2023-07-28 12:35 ` Miquel Raynal
2023-07-16 14:46 ` [PATCH 3/8] mtd: rawnand: qcom: Fix alignment with open parenthesis Miquel Raynal
2023-07-17 2:27 ` Manivannan Sadhasivam
2023-07-28 2:17 ` Tudor Ambarus
2023-07-16 14:46 ` [PATCH 4/8] mtd: rawnand: qcom: Fix the spacing Miquel Raynal
2023-07-17 2:28 ` Manivannan Sadhasivam
2023-07-28 2:18 ` Tudor Ambarus
2023-07-28 12:34 ` Miquel Raynal
2023-07-16 14:46 ` [PATCH 5/8] mtd: rawnand: qcom: Fix wrong indentation Miquel Raynal
2023-07-17 2:29 ` Manivannan Sadhasivam
2023-07-28 2:20 ` Tudor Ambarus
2023-07-28 12:34 ` Miquel Raynal
2023-07-16 14:46 ` [PATCH 6/8] mtd: rawnand: qcom: Fix a typo Miquel Raynal
2023-07-17 2:30 ` Manivannan Sadhasivam
2023-07-28 2:22 ` Tudor Ambarus
2023-07-28 12:34 ` Miquel Raynal
2023-07-16 14:46 ` [PATCH 7/8] mtd: rawnand: qcom: Early structure initialization Miquel Raynal
2023-07-17 2:31 ` Manivannan Sadhasivam
2023-07-27 15:03 ` Tudor Ambarus
2023-07-27 15:14 ` Miquel Raynal
2023-07-28 2:23 ` Tudor Ambarus
2023-07-28 12:34 ` Miquel Raynal
2023-07-16 14:46 ` [PATCH 8/8] mtd: rawnand: qcom: Fix address parsing within ->exec_op() Miquel Raynal
2023-07-17 6:38 ` Manivannan Sadhasivam
2023-07-27 14:59 ` Miquel Raynal [this message]
2023-07-28 2:31 ` Tudor Ambarus
2023-07-28 7:56 ` Miquel Raynal
2023-07-28 2:33 ` Sricharan Ramabadhran
2023-07-28 4:14 ` Sricharan Ramabadhran
2023-07-28 7:55 ` Miquel Raynal
2023-07-28 2:27 ` Tudor Ambarus
2023-07-28 12:34 ` Miquel Raynal
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=20230727165923.32488041@xps-13 \
--to=miquel.raynal@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=lkp@intel.com \
--cc=mani@kernel.org \
--cc=michael@walle.cc \
--cc=pratyush@kernel.org \
--cc=quic_mdalam@quicinc.com \
--cc=quic_srichara@quicinc.com \
--cc=richard@nod.at \
--cc=tudor.ambarus@linaro.org \
--cc=vigneshr@ti.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