mtd: spi-nor: Skip erase logic when SPI_NOR_NO_ERASE is set
[ Upstream commit 151c6b49d679872d6fc0b50e0ad96303091694a2 ]
Even if SPI_NOR_NO_ERASE was set, one could still send erase opcodes
to the flash. It is not recommended to send unsupported opcodes to
flashes. Fix the logic and do not set mtd->_erase when SPI_NOR_NO_ERASE
is specified. With this users will not be able to issue erase opcodes to
flashes and instead they will recive an -ENOTSUPP error.
Fixes: b199489d37 ("mtd: spi-nor: add the framework for SPI NOR")
Signed-off-by: Tudor Ambarus <tudor.ambarus@microchip.com>
Reviewed-by: Michael Walle <michael@walle.cc>
Cc: stable@vger.kernel.org
Link: https://lore.kernel.org/r/20220228163334.277730-1-tudor.ambarus@microchip.com
Signed-off-by: Sasha Levin <sashal@kernel.org>
This commit is contained in:
committed by
Greg Kroah-Hartman
parent
e65d78b12f
commit
a1e69c36de
@@ -3148,7 +3148,6 @@ int spi_nor_scan(struct spi_nor *nor, const char *name,
|
|||||||
mtd->writesize = nor->params->writesize;
|
mtd->writesize = nor->params->writesize;
|
||||||
mtd->flags = MTD_CAP_NORFLASH;
|
mtd->flags = MTD_CAP_NORFLASH;
|
||||||
mtd->size = nor->params->size;
|
mtd->size = nor->params->size;
|
||||||
mtd->_erase = spi_nor_erase;
|
|
||||||
mtd->_read = spi_nor_read;
|
mtd->_read = spi_nor_read;
|
||||||
mtd->_suspend = spi_nor_suspend;
|
mtd->_suspend = spi_nor_suspend;
|
||||||
mtd->_resume = spi_nor_resume;
|
mtd->_resume = spi_nor_resume;
|
||||||
@@ -3178,6 +3177,8 @@ int spi_nor_scan(struct spi_nor *nor, const char *name,
|
|||||||
|
|
||||||
if (info->flags & SPI_NOR_NO_ERASE)
|
if (info->flags & SPI_NOR_NO_ERASE)
|
||||||
mtd->flags |= MTD_NO_ERASE;
|
mtd->flags |= MTD_NO_ERASE;
|
||||||
|
else
|
||||||
|
mtd->_erase = spi_nor_erase;
|
||||||
|
|
||||||
mtd->dev.parent = dev;
|
mtd->dev.parent = dev;
|
||||||
nor->page_size = nor->params->page_size;
|
nor->page_size = nor->params->page_size;
|
||||||
|
|||||||
Reference in New Issue
Block a user