From: Jiri Slaby <jirislaby@kernel.org>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
Jiasheng Jiang <jiashengjiangcool@gmail.com>
Cc: gmpy.liaowx@gmail.com, kees@kernel.org,
linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
miquel.raynal@bootlin.com, richard@nod.at, vigneshr@ti.com,
stable@vger.kernel.org
Subject: Re: [PATCH v2] mtd: Add check and kfree() for kcalloc()
Date: Tue, 4 Feb 2025 07:36:14 +0100 [thread overview]
Message-ID: <48ad8f05-a90b-499d-9e73-8e5ff032824a@kernel.org> (raw)
In-Reply-To: <e41d9378-e5e5-478d-bead-aa50a9f79d4d@wanadoo.fr>
On 04. 02. 25, 7:17, Christophe JAILLET wrote:
> Le 04/02/2025 à 03:33, Jiasheng Jiang a écrit :
>> Add a check for kcalloc() to ensure successful allocation.
>> Moreover, add kfree() in the error-handling path to prevent memory leaks.
>>
>> Fixes: 78c08247b9d3 ("mtd: Support kmsg dumper based on pstore/blk")
>> Cc: <stable@vger.kernel.org> # v5.10+
>> Signed-off-by: Jiasheng Jiang <jiashengjiangcool@gmail.com>
>> ---
>> Changelog:
>>
>> v1 -> v2:
>>
>> 1. Remove redundant logging.
>> 2. Add kfree() in the error-handling path.
>> ---
>> drivers/mtd/mtdpstore.c | 19 ++++++++++++++++++-
>> 1 file changed, 18 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/mtd/mtdpstore.c b/drivers/mtd/mtdpstore.c
>> index 7ac8ac901306..2d8e330dd215 100644
>> --- a/drivers/mtd/mtdpstore.c
>> +++ b/drivers/mtd/mtdpstore.c
>> @@ -418,10 +418,17 @@ static void mtdpstore_notify_add(struct mtd_info
>> *mtd)
>> longcnt = BITS_TO_LONGS(div_u64(mtd->size, info->kmsg_size));
>> cxt->rmmap = kcalloc(longcnt, sizeof(long), GFP_KERNEL);
>> + if (!cxt->rmmap)
>> + goto end;
>
> Nitpick: Could be a direct return.
>
>> +
>> cxt->usedmap = kcalloc(longcnt, sizeof(long), GFP_KERNEL);
>> + if (!cxt->usedmap)
>> + goto free_rmmap;
>> longcnt = BITS_TO_LONGS(div_u64(mtd->size, mtd->erasesize));
>> cxt->badmap = kcalloc(longcnt, sizeof(long), GFP_KERNEL);
>> + if (!cxt->badmap)
>> + goto free_usedmap;
>> /* just support dmesg right now */
>> cxt->dev.flags = PSTORE_FLAGS_DMESG;
>> @@ -435,10 +442,20 @@ static void mtdpstore_notify_add(struct mtd_info
>> *mtd)
>> if (ret) {
>> dev_err(&mtd->dev, "mtd%d register to psblk failed\n",
>> mtd->index);
>> - return;
>> + goto free_badmap;
>> }
>> cxt->mtd = mtd;
>> dev_info(&mtd->dev, "Attached to MTD device %d\n", mtd->index);
>> + goto end;
>
> Mater of taste, but I think that having an explicit return here would be
> clearer that a goto end;
Yes, drop the whole end.
>> +free_badmap:
>> + kfree(cxt->badmap);
>> +free_usedmap:
>> + kfree(cxt->usedmap);
>> +free_rmmap:
>> + kfree(cxt->rmmap);
>
> I think that in all these paths, you should also have
> cxt->XXXmap = NULL;
> after the kfree().
>
> otherwise when mtdpstore_notify_remove() is called, you could have a
> double free.
Right, and this is already a problem for failing
register_pstore_device() in _add() -- there is unconditional
unregister_pstore_device() in _remove(). Should _remove() check cxt->mtd
first?
thanks,
--
js
suse labs
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2025-02-04 6:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-02 20:54 [PATCH] mtd: Add check for kcalloc() Jiasheng Jiang
2025-02-03 8:32 ` Miquel Raynal
2025-02-03 18:04 ` Christophe JAILLET
2025-02-04 2:33 ` [PATCH v2] mtd: Add check and kfree() " Jiasheng Jiang
2025-02-04 6:17 ` Christophe JAILLET
2025-02-04 6:36 ` Jiri Slaby [this message]
2025-02-04 20:50 ` Christophe JAILLET
2025-02-05 2:31 ` [PATCH v3 1/2] mtd: Replace kcalloc() with devm_kcalloc() Jiasheng Jiang
2025-02-05 2:31 ` [PATCH v3 2/2] mtd: Add check for devm_kcalloc() Jiasheng Jiang
2025-02-07 14:46 ` [PATCH v3 1/2] mtd: Replace kcalloc() with devm_kcalloc() Miquel Raynal
2025-02-05 2:35 ` [PATCH v2] mtd: Add check and kfree() for kcalloc() Jiasheng Jiang
2025-02-04 6:32 ` Jiri Slaby
2025-02-04 9:17 ` Miquel Raynal
2025-02-04 2:37 ` [PATCH] mtd: Add check " Jiasheng Jiang
2025-02-04 2:34 ` Jiasheng Jiang
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=48ad8f05-a90b-499d-9e73-8e5ff032824a@kernel.org \
--to=jirislaby@kernel.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=gmpy.liaowx@gmail.com \
--cc=jiashengjiangcool@gmail.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=stable@vger.kernel.org \
--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