From: "Michal Nazarewicz" <mina86@mina86.com>
To: "Felipe Balbi" <balbi@ti.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Yongsul Oh" <yongsul96.oh@samsung.com>
Cc: "Michal Nazarewicz" <mnazarewicz@gmail.com>,
"Sergei Shtylyov" <sshtylyov@mvista.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] USB: Gadget: Composite: Added error handling codes to prevent a memory leak case when the configuration's bind function failed
Date: Tue, 20 Mar 2012 14:41:30 +0100 [thread overview]
Message-ID: <op.wbg1ngqj3l0zgt@mpn-glaptop> (raw)
In-Reply-To: <1332207518-24868-1-git-send-email-yongsul96.oh@samsung.com>
On Tue, 20 Mar 2012 02:38:38 +0100, Yongsul Oh <yongsul96.oh@samsung.com> wrote:
> In some USB composite gadget drivers, the configuration's bind function
> called by the usb_add_config() calls multiple bind config functions.
> (for example cdc2 configuration bind function in the cdc_do_config()
> of the cdc2.c has two functionality bind config functions.
> - the ecm_bind_config() & the acm_bind_config())
>
> In each functionality bind config function, new instance is allocated and
> finally added by the usb_add_function().
>
> So if an error occurred during the second functionality bind config
> (for example an error occurred at the acm_bind_config() after succeeding of
> the ecm_bind_function()), the instance created by the acm_bind_config()
> cannot be freed creating a memory leak.
>
> This patch fixes this issue.
>
> Signed-off-by: Yongsul Oh <yongsul96.oh@samsung.com>
Like before:
Acked-by: Michal Nazarewicz <mina86@mina86.com>
> ---
> drivers/usb/gadget/composite.c | 13 +++++++++++++
> 1 files changed, 13 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/usb/gadget/composite.c b/drivers/usb/gadget/composite.c
> index baaebf2..4cb1801 100644
> --- a/drivers/usb/gadget/composite.c
> +++ b/drivers/usb/gadget/composite.c
> @@ -737,6 +737,19 @@ int usb_add_config(struct usb_composite_dev *cdev,
> status = bind(config);
> if (status < 0) {
> + while (!list_empty(&config->functions)) {
> + struct usb_function *f;
> +
> + f = list_first_entry(&config->functions,
> + struct usb_function, list);
> + list_del(&f->list);
> + if (f->unbind) {
> + DBG(cdev, "unbind function '%s'/%p\n",
> + f->name, f);
> + f->unbind(config, f);
> + /* may free memory for "f" */
> + }
> + }
> list_del(&config->list);
> config->cdev = NULL;
> } else {
--
Best regards, _ _
.o. | Liege of Serenely Enlightened Majesty of o' \,=./ `o
..o | Computer Science, Michał “mina86” Nazarewicz (o o)
ooo +----<email/xmpp: mpn@google.com>--------------ooO--(_)--Ooo--
next prev parent reply other threads:[~2012-03-20 13:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 1:38 Yongsul Oh
2012-03-20 13:41 ` Michal Nazarewicz [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-03-16 6:27 Yongsul Oh
2012-03-16 11:14 ` Michal Nazarewicz
2012-03-19 8:34 ` Yongsul Oh
2012-03-15 1:23 Yongsul, Oh
2012-03-15 8:19 ` Michal Nazarewicz
2012-03-15 13:57 ` Sergei Shtylyov
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=op.wbg1ngqj3l0zgt@mpn-glaptop \
--to=mina86@mina86.com \
--cc=balbi@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mnazarewicz@gmail.com \
--cc=sshtylyov@mvista.com \
--cc=yongsul96.oh@samsung.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
all inboxes | Powered by JetHome®