From: <Tudor.Ambarus@microchip.com>
To: <yangyicong@hisilicon.com>, <p.yadav@ti.com>, <michael@walle.cc>,
<linux-mtd@lists.infradead.org>
Cc: <miquel.raynal@bootlin.com>, <richard@nod.at>, <vigneshr@ti.com>,
<linuxarm@huawei.com>, <prime.zeng@huawei.com>
Subject: Re: [PATCH RESEND] mtd:spi-nor: Fix an issue of releasing resources during read/write
Date: Fri, 9 Apr 2021 03:21:37 +0000 [thread overview]
Message-ID: <a77d9b48-e7c4-044f-3c14-25bcc817b43f@microchip.com> (raw)
In-Reply-To: <1617262486-4223-1-git-send-email-yangyicong@hisilicon.com>
On 4/1/21 10:34 AM, Yicong Yang wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> From: Xiang Chen <chenxiang66@hisilicon.com>
>
> If rmmod the driver during read or write, the driver will release the
> resources which are used during read or write, so it is possible to
> refer to NULL pointer.
>
> Use the testcase "mtd_debug read /dev/mtd0 0xc00000 0x400000 dest_file &
> sleep 0.5;rmmod spi_hisi_sfc_v3xx.ko", the issue can be reproduced in
> hisi_sfc_v3xx driver.
>
> To avoid the issue, fill the interface _get_device and _put_device of
> mtd_info to grab the reference to the spi controller driver module, so
> the request of rmmod the driver is rejected before read/write is finished.
>
Do we care for a Fixes tag and a Cc to stable? I guess this bug is present
since the introduction of the driver.
> Signed-off-by: Xiang Chen <chenxiang66@hisilicon.com>
> Signed-off-by: Yicong Yang <yangyicong@hisilicon.com>
Tested-by: Tudor Ambarus <tudor.ambarus@microchip.com>
Will fix the subject of the commit when applying.
Thanks,
ta
> ---
> drivers/mtd/spi-nor/core.c | 33 +++++++++++++++++++++++++++++++++
> 1 file changed, 33 insertions(+)
>
> diff --git a/drivers/mtd/spi-nor/core.c b/drivers/mtd/spi-nor/core.c
> index 0522304..72bc134 100644
> --- a/drivers/mtd/spi-nor/core.c
> +++ b/drivers/mtd/spi-nor/core.c
> @@ -3301,6 +3301,37 @@ static void spi_nor_resume(struct mtd_info *mtd)
> dev_err(dev, "resume() failed\n");
> }
>
> +static int spi_nor_get_device(struct mtd_info *mtd)
> +{
> + struct mtd_info *master = mtd_get_master(mtd);
> + struct spi_nor *nor = mtd_to_spi_nor(master);
> + struct device *dev;
> +
> + if (nor->spimem)
> + dev = nor->spimem->spi->controller->dev.parent;
> + else
> + dev = nor->dev;
> +
> + if (!try_module_get(dev->driver->owner))
> + return -ENODEV;
> +
> + return 0;
> +}
> +
> +static void spi_nor_put_device(struct mtd_info *mtd)
> +{
> + struct mtd_info *master = mtd_get_master(mtd);
> + struct spi_nor *nor = mtd_to_spi_nor(master);
> + struct device *dev;
> +
> + if (nor->spimem)
> + dev = nor->spimem->spi->controller->dev.parent;
> + else
> + dev = nor->dev;
> +
> + module_put(dev->driver->owner);
> +}
> +
> void spi_nor_restore(struct spi_nor *nor)
> {
> /* restore the addressing mode */
> @@ -3495,6 +3526,8 @@ int spi_nor_scan(struct spi_nor *nor, const char *name,
> mtd->_read = spi_nor_read;
> mtd->_suspend = spi_nor_suspend;
> mtd->_resume = spi_nor_resume;
> + mtd->_get_device = spi_nor_get_device;
> + mtd->_put_device = spi_nor_put_device;
>
> if (nor->params->locking_ops) {
> mtd->_lock = spi_nor_lock;
> --
> 2.8.1
>
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2021-04-09 3:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 7:34 [PATCH RESEND] mtd:spi-nor: Fix an issue of releasing resources during read/write Yicong Yang
2021-04-07 14:50 ` Michael Walle
2021-04-08 11:10 ` Yicong Yang
2021-04-09 3:21 ` Tudor.Ambarus [this message]
2021-04-09 4:03 ` Yicong Yang
2021-04-09 4:13 ` Tudor.Ambarus
2021-04-09 6:05 ` Yicong Yang
2021-04-11 7:45 ` Tudor Ambarus
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=a77d9b48-e7c4-044f-3c14-25bcc817b43f@microchip.com \
--to=tudor.ambarus@microchip.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxarm@huawei.com \
--cc=michael@walle.cc \
--cc=miquel.raynal@bootlin.com \
--cc=p.yadav@ti.com \
--cc=prime.zeng@huawei.com \
--cc=richard@nod.at \
--cc=vigneshr@ti.com \
--cc=yangyicong@hisilicon.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