From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: Richard Weinberger <richard@nod.at>,
David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
Marek Vasut <marek.vasut@gmail.com>,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mtd: rawnand: tegra: fix error handling of subop helpers
Date: Tue, 17 Jul 2018 14:38:41 +0200 [thread overview]
Message-ID: <20180717143841.3e8cbd88@bbrezillon> (raw)
In-Reply-To: <20180717142254.61998c98@xps13>
On Tue, 17 Jul 2018 14:22:54 +0200
Miquel Raynal <miquel.raynal@bootlin.com> wrote:
> Hi Boris,
>
> Boris Brezillon <boris.brezillon@bootlin.com> wrote on Tue, 17 Jul 2018
> 14:17:33 +0200:
>
> > On Sat, 14 Jul 2018 18:32:51 +0200
> > Miquel Raynal <miquel.raynal@bootlin.com> wrote:
> >
> > > A report from Colin Ian King pointed a CoverityScan issue where error
> > > values on these helpers where not checked in the drivers. These
> > > helpers could error out only in case of a software bug in driver code,
> > > not because of a runtime/hardware error but in any cases it is safer
> > > to handle these errors properly.
> > >
> > > Fix the Tegra NAND controller driver implementation by checking
> > > potential negative error values coming from these helpers.
> >
> > Hm, ok. I thought you were opting for a return 0 + WARN_ON() approach,
> > what made you change your mind?
>
> Wise people told me WARN_ON() should be avoided as much as possible.
I think I mentioned BUG_ON(), not WARN_ON() :P.
> Hence after more discussion with myself I choose to implement the most
> standard C solution: check the returned value...
>
> But if you think a return 0 + WARN_ON() would be better I'm ready to
> change this as it was my initial idea :)
Well, if this cannot happen without a SW bug, then I'd recommend the
WARN_ON() + unsigned int ret approach. That should force people debug
their implementation while keeping drivers code simple.
>
> >
> > >
> > > Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
> > > ---
> > >
> > > This patch should have been part of the following series:
> > > http://lists.infradead.org/pipermail/linux-mtd/2018-July/082654.html
> > > It will be squashed with original commit introducing this driver.
> > >
> > > Thanks,
> > > Miquèl
> > >
> > > drivers/mtd/nand/raw/tegra_nand.c | 7 +++++++
> > > 1 file changed, 7 insertions(+)
> > >
> > > diff --git a/drivers/mtd/nand/raw/tegra_nand.c b/drivers/mtd/nand/raw/tegra_nand.c
> > > index 22d6a7f9ff80..59ead8f41718 100644
> > > --- a/drivers/mtd/nand/raw/tegra_nand.c
> > > +++ b/drivers/mtd/nand/raw/tegra_nand.c
> > > @@ -379,6 +379,9 @@ static int tegra_nand_cmd(struct nand_chip *chip,
> > > case NAND_OP_ADDR_INSTR:
> > > offset = nand_subop_get_addr_start_off(subop, op_id);
> > > naddrs = nand_subop_get_num_addr_cyc(subop, op_id);
> > > + if (offset < 0 || naddrs < 0)
> > > + return -EINVAL;
> > > +
> > > addrs = &instr->ctx.addr.addrs[offset];
> > >
> > > cmd |= COMMAND_ALE | COMMAND_ALE_SIZE(naddrs);
> > > @@ -395,6 +398,8 @@ static int tegra_nand_cmd(struct nand_chip *chip,
> > > case NAND_OP_DATA_IN_INSTR:
> > > size = nand_subop_get_data_len(subop, op_id);
> > > offset = nand_subop_get_data_start_off(subop, op_id);
> > > + if (size < 0 || offset < 0)
> > > + return -EINVAL;
> > >
> > > cmd |= COMMAND_TRANS_SIZE(size) | COMMAND_PIO |
> > > COMMAND_RX | COMMAND_A_VALID;
> > > @@ -405,6 +410,8 @@ static int tegra_nand_cmd(struct nand_chip *chip,
> > > case NAND_OP_DATA_OUT_INSTR:
> > > size = nand_subop_get_data_len(subop, op_id);
> > > offset = nand_subop_get_data_start_off(subop, op_id);
> > > + if (size < 0 || offset < 0)
> > > + return -EINVAL;
> > >
> > > cmd |= COMMAND_TRANS_SIZE(size) | COMMAND_PIO |
> > > COMMAND_TX | COMMAND_A_VALID;
> >
>
>
>
next prev parent reply other threads:[~2018-07-17 12:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-14 16:32 [PATCH] mtd: rawnand: tegra: fix error handling of subop helpers Miquel Raynal
2018-07-17 12:17 ` Boris Brezillon
2018-07-17 12:22 ` Miquel Raynal
2018-07-17 12:38 ` Boris Brezillon [this message]
2018-07-17 12:41 ` 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=20180717143841.3e8cbd88@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
/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;
as well as URLs for NNTP newsgroup(s).