From: Firo Yang <firogm@gmail.com>
To: kernel-janitors@vger.kernel.org
Subject: [PATCH v3] firmware: Fix memory leak in error path
Date: Sat, 06 Jun 2015 05:48:15 +0000 [thread overview]
Message-ID: <1433569695-19348-1-git-send-email-firogm@gmail.com> (raw)
Eliminate a memory leak by unifying the error handling code
at the end of the function.
Signed-off-by: Firo Yang <firogm@gmail.com>
---
drivers/base/firmware_class.c | 19 ++++++++++++++-----
1 file changed, 14 insertions(+), 5 deletions(-)
diff --git a/drivers/base/firmware_class.c b/drivers/base/firmware_class.c
index 8c3aa3c..5bb098b 100644
--- a/drivers/base/firmware_class.c
+++ b/drivers/base/firmware_class.c
@@ -1299,6 +1299,7 @@ request_firmware_nowait(
const char *name, struct device *device, gfp_t gfp, void *context,
void (*cont)(const struct firmware *fw, void *context))
{
+ int rc;
struct firmware_work *fw_work;
fw_work = kzalloc(sizeof(struct firmware_work), gfp);
@@ -1307,8 +1308,11 @@ request_firmware_nowait(
fw_work->module = module;
fw_work->name = kstrdup_const(name, gfp);
- if (!fw_work->name)
- return -ENOMEM;
+ if (!fw_work->name) {
+ rc = -ENOMEM;
+ goto free_work;
+ }
+
fw_work->device = device;
fw_work->context = context;
fw_work->cont = cont;
@@ -1316,15 +1320,20 @@ request_firmware_nowait(
(uevent ? FW_OPT_UEVENT : FW_OPT_USERHELPER);
if (!try_module_get(module)) {
- kfree_const(fw_work->name);
- kfree(fw_work);
- return -EFAULT;
+ rc = -EFAULT;
+ goto free_name;
}
get_device(fw_work->device);
INIT_WORK(&fw_work->work, request_firmware_work_func);
schedule_work(&fw_work->work);
return 0;
+
+free_name:
+ kfree_const(fw_work->name);
+free_work:
+ kfree(fw_work);
+ return rc;
}
EXPORT_SYMBOL(request_firmware_nowait);
--
2.4.2
next reply other threads:[~2015-06-06 5:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-06 5:48 Firo Yang [this message]
2015-06-06 5:58 ` [PATCH v3] firmware: Fix memory leak in error path Ming Lei
2015-08-05 22:10 ` Greg KH
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=1433569695-19348-1-git-send-email-firogm@gmail.com \
--to=firogm@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.