From: Greg KH <gregkh@linuxfoundation.org>
To: Kunwu Chan <chentao@kylinos.cn>
Cc: joel@jms.id.au, andrew@codeconstruct.com.au,
andriy.shevchenko@linux.intel.com, linux-usb@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, kunwu.chan@hotmail.com,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: gadget: aspeed: Check return value of kasprintf in ast_vhub_alloc_epn
Date: Wed, 22 Nov 2023 12:10:34 +0000 [thread overview]
Message-ID: <2023112236-bullseye-pranker-491e@gregkh> (raw)
In-Reply-To: <20231122014212.304254-1-chentao@kylinos.cn>
On Wed, Nov 22, 2023 at 09:42:12AM +0800, Kunwu Chan wrote:
> kasprintf() returns a pointer to dynamically allocated memory
> which can be NULL upon failure. Ensure the allocation was successful
> by checking the pointer validity.
>
> Signed-off-by: Kunwu Chan <chentao@kylinos.cn>
> ---
> drivers/usb/gadget/udc/aspeed-vhub/epn.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/usb/gadget/udc/aspeed-vhub/epn.c b/drivers/usb/gadget/udc/aspeed-vhub/epn.c
> index 148d7ec3ebf4..e0854e878411 100644
> --- a/drivers/usb/gadget/udc/aspeed-vhub/epn.c
> +++ b/drivers/usb/gadget/udc/aspeed-vhub/epn.c
> @@ -826,6 +826,8 @@ struct ast_vhub_ep *ast_vhub_alloc_epn(struct ast_vhub_dev *d, u8 addr)
> ep->vhub = vhub;
> ep->ep.ops = &ast_vhub_epn_ops;
> ep->ep.name = kasprintf(GFP_KERNEL, "ep%d", addr);
> + if (!ep->ep.name)
> + return NULL;
This will break things if this ever triggers. How was this tested? The
"slot" for this device will still be seen as used and so the resources
never freed and then you can run out of space for real devices, right?
Looks like the other error handling in this function below this call is
also broken, can you fix that up too?
thanks,
greg k-h
next prev parent reply other threads:[~2023-11-22 12:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 1:42 [PATCH] usb: gadget: aspeed: Check return value of kasprintf in ast_vhub_alloc_epn Kunwu Chan
2023-11-22 10:48 ` Andy Shevchenko
2023-11-22 12:10 ` Greg KH [this message]
2024-01-11 9:31 ` Kunwu Chan
2024-01-11 10:03 ` 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=2023112236-bullseye-pranker-491e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=andrew@codeconstruct.com.au \
--cc=andriy.shevchenko@linux.intel.com \
--cc=chentao@kylinos.cn \
--cc=joel@jms.id.au \
--cc=kunwu.chan@hotmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox