From: coverity-bot <keescook@chromium.org>
To: Tudor Ambarus <tudor.ambarus@microchip.com>
Cc: Boris Brezillon <boris.brezillon@collabora.com>,
"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
linux-next@vger.kernel.org
Subject: Coverity: spi_nor_erase_sector(): Null pointer dereferences
Date: Mon, 28 Oct 2019 16:05:49 -0700 [thread overview]
Message-ID: <201910281605.9E90B64E86@keescook> (raw)
Hello!
This is an experimental automated report about issues detected by Coverity
from a scan of next-20191025 as part of the linux-next weekly scan project:
https://scan.coverity.com/projects/linux-next-weekly-scan
You're getting this email because you were associated with the identified
lines of code (noted below) that were touched by recent commits:
453977875364 ("mtd: spi-nor: Introduce 'struct spi_nor_controller_ops'")
Coverity reported the following:
*** CID 1487363: Null pointer dereferences (FORWARD_NULL)
/drivers/mtd/spi-nor/spi-nor.c: 967 in spi_nor_erase_sector()
961 */
962 for (i = nor->addr_width - 1; i >= 0; i--) {
963 nor->bouncebuf[i] = addr & 0xff;
964 addr >>= 8;
965 }
966
vvv CID 1487363: Null pointer dereferences (FORWARD_NULL)
vvv Dereferencing null pointer "nor->controller_ops".
967 return nor->controller_ops->write_reg(nor, nor->erase_opcode,
968 nor->bouncebuf, nor->addr_width);
969 }
970
971 /**
972 * spi_nor_div_by_erase_size() - calculate remainder and update new dividend
If this is a false positive, please let us know so we can mark it as
such, or teach the Coverity rules to be smarter. If not, please make
sure fixes get into linux-next. :) For patches fixing this, please
include:
Reported-by: coverity-bot <keescook+coverity-bot@chromium.org>
Addresses-Coverity-ID: 1487363 ("Null pointer dereferences")
Fixes: 453977875364 ("mtd: spi-nor: Introduce 'struct spi_nor_controller_ops'")
Thanks for your attention!
--
Coverity-bot
next reply other threads:[~2019-10-28 23:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-28 23:05 coverity-bot [this message]
2019-10-29 5:59 ` Coverity: spi_nor_erase_sector(): Null pointer dereferences Tudor.Ambarus
2019-10-29 16:05 ` Kees Cook
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=201910281605.9E90B64E86@keescook \
--to=keescook@chromium.org \
--cc=boris.brezillon@collabora.com \
--cc=gustavo@embeddedor.com \
--cc=linux-next@vger.kernel.org \
--cc=tudor.ambarus@microchip.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