From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Ansuel Smith <ansuelsmth@gmail.com>
Cc: Andy Gross <agross@kernel.org>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Manivannan Sadhasivam <mani@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-mtd@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mtd: parsers: qcom: Fix leaking of partition name
Date: Mon, 24 May 2021 22:38:29 -0500 [thread overview]
Message-ID: <YKxxNY8d/M1fXWr9@yoga> (raw)
In-Reply-To: <20210525001449.10386-1-ansuelsmth@gmail.com>
On Mon 24 May 19:14 CDT 2021, Ansuel Smith wrote:
> Partition name are already allocated and defined by the ptable struct.
> Skip reallocation of name variable and directly lowercase the name in
> the ptable struct. The name variable was duplicated but never freed.
> The leak was found using kmemleak.
>
We know that SMEM_AARM_PARTITION_TABLE is accessed by at least the modem
firmware, so I don't think we should change it in place.
I think the appropriate solution is to implement the "cleanup" operation
in struct mtd_part_parser.
Regards,
Bjorn
> Fixes: 803eb124e1a6 ("mtd: parsers: Add Qcom SMEM parser")
> Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
> ---
> drivers/mtd/parsers/qcomsmempart.c | 22 ++++------------------
> 1 file changed, 4 insertions(+), 18 deletions(-)
>
> diff --git a/drivers/mtd/parsers/qcomsmempart.c b/drivers/mtd/parsers/qcomsmempart.c
> index d9083308f6ba..3d083f0815f8 100644
> --- a/drivers/mtd/parsers/qcomsmempart.c
> +++ b/drivers/mtd/parsers/qcomsmempart.c
> @@ -62,8 +62,8 @@ static int parse_qcomsmem_part(struct mtd_info *mtd,
> struct smem_flash_ptable *ptable;
> size_t len = SMEM_FLASH_PTABLE_HDR_LEN;
> struct mtd_partition *parts;
> - int ret, i, numparts;
> - char *name, *c;
> + int i, numparts;
> + char *c;
>
> if (IS_ENABLED(CONFIG_MTD_SPI_NOR_USE_4K_SECTORS)
> && mtd->type == MTD_NORFLASH) {
> @@ -125,17 +125,11 @@ static int parse_qcomsmem_part(struct mtd_info *mtd,
> if (pentry->name[0] == '\0')
> continue;
>
> - name = kstrdup(pentry->name, GFP_KERNEL);
> - if (!name) {
> - ret = -ENOMEM;
> - goto out_free_parts;
> - }
> -
> /* Convert name to lower case */
> - for (c = name; *c != '\0'; c++)
> + for (c = pentry->name; *c != '\0'; c++)
> *c = tolower(*c);
>
> - parts[i].name = name;
> + parts[i].name = pentry->name;
> parts[i].offset = le32_to_cpu(pentry->offset) * mtd->erasesize;
> parts[i].mask_flags = pentry->attr;
> parts[i].size = le32_to_cpu(pentry->length) * mtd->erasesize;
> @@ -149,14 +143,6 @@ static int parse_qcomsmem_part(struct mtd_info *mtd,
> *pparts = parts;
>
> return numparts;
> -
> -out_free_parts:
> - while (--i >= 0)
> - kfree(parts[i].name);
> - kfree(parts);
> - *pparts = NULL;
> -
> - return ret;
> }
>
> static const struct of_device_id qcomsmem_of_match_table[] = {
> --
> 2.31.1
>
prev parent reply other threads:[~2021-05-25 3:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 0:14 [PATCH] mtd: parsers: qcom: Fix leaking of partition name Ansuel Smith
2021-05-25 3:38 ` Bjorn Andersson [this message]
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=YKxxNY8d/M1fXWr9@yoga \
--to=bjorn.andersson@linaro.org \
--cc=agross@kernel.org \
--cc=ansuelsmth@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mani@kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--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;
as well as URLs for NNTP newsgroup(s).