From: Greg KH <gregkh@linuxfoundation.org>
To: Loke Forsberg <loke.forsberg@gmail.com>
Cc: linux-usb@vger.kernel.org, khtsai@google.com,
raubcameo@gmail.com, kees@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: gadget: f_ncm: replace kzalloc with kzalloc_obj
Date: Mon, 16 Mar 2026 07:07:53 +0100 [thread overview]
Message-ID: <2026031617-hypocrisy-lion-cb8e@gregkh> (raw)
In-Reply-To: <20260315111827.20205-1-Loke.Forsberg@gmail.com>
On Sun, Mar 15, 2026 at 12:18:27PM +0100, Loke Forsberg wrote:
> Replace kzalloc(sizeof(*ptr)) with kzalloc_obj(), to improve type safety.
>
> Signed-off-by: Loke Forsberg <Loke.Forsberg@gmail.com>
> ---
> drivers/usb/gadget/function/f_ncm.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/usb/gadget/function/f_ncm.c b/drivers/usb/gadget/function/f_ncm.c
> index 14fc7dce6f39..e1e6763293ef 100644
> --- a/drivers/usb/gadget/function/f_ncm.c
> +++ b/drivers/usb/gadget/function/f_ncm.c
> @@ -1456,7 +1456,7 @@ static int ncm_bind(struct usb_configuration *c, struct usb_function *f)
> return -EINVAL;
>
> if (cdev->use_os_string) {
> - os_desc_table = kzalloc(sizeof(*os_desc_table), GFP_KERNEL);
> + os_desc_table = kzalloc_obj(os_desc_table, GFP_KERNEL);
Why have you used GFP_KERNEL when kzalloc_obj() does not need that for
the default case?
> if (!os_desc_table)
> return -ENOMEM;
> }
> @@ -1753,7 +1753,7 @@ static struct usb_function *ncm_alloc(struct usb_function_instance *fi)
> struct f_ncm_opts *opts;
>
> /* allocate and initialize one new instance */
> - ncm = kzalloc(sizeof(*ncm), GFP_KERNEL);
> + ncm = kzalloc_obj(ncm, GFP_KERNEL);
Same here.
thanks,
greg k-h
next prev parent reply other threads:[~2026-03-16 6:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-15 11:18 [PATCH] usb: gadget: f_ncm: replace kzalloc with kzalloc_obj Loke Forsberg
2026-03-16 6:07 ` Greg KH [this message]
2026-03-16 9:08 ` Loke Forsberg
2026-03-19 20:38 ` Kees Cook
2026-03-19 21:11 ` Kees Cook
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=2026031617-hypocrisy-lion-cb8e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=kees@kernel.org \
--cc=khtsai@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=loke.forsberg@gmail.com \
--cc=raubcameo@gmail.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 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.