From: sashiko-bot@kernel.org
To: "Anfernee Cao" <anferneemelokc5@gmail.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: [PATCH] usb: musb: fix double put of gadget device on setup failure
Date: Tue, 20 Oct 2026 14:31:44 +0000 [thread overview]
Message-ID: <sashiko-outbox-179144@kernel.org> (raw)
In-Reply-To: <179250629747.20696.17364135141613638741@gmail.com>
> musb_gadget_setup() calls usb_add_gadget_udc() and, when that fails,
> calls device_unregister(&musb->g.dev). But usb_add_gadget_udc() already
> releases the gadget on failure: usb_add_gadget_udc_release() calls
> usb_put_gadget(), i.e. put_device(&gadget->dev), in its error path.
>
> The device model documents the same rule in the kerneldoc of
> device_register() (drivers/base/core.c):
>
> NOTE: _Never_ directly free @dev after calling this function, even
> if it returned an error! Always use put_device() to give up the
> reference initialized in this function instead.
>
> The extra device_unregister() therefore runs device_del() on a device
> that was never added (or was already deleted) and drops the reference a
> second time, causing a refcount underflow.
>
> Drop the redundant cleanup and just return the error; the UDC core has
> already released the gadget.
>
> This issue was found by manual code inspection.
>
> Fixes: 3301c215a2bb ("USB: UDC: Expand device model API interface")
> Cc: stable@vger.kernel.org # v5.10+
> Signed-off-by: Anfernee Cao <anferneemelokc5@gmail.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/179250629747.20696.17364135141613638741@gmail.com?part=1
prev parent reply other threads:[~2026-10-20 14:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 14:24 [PATCH] usb: musb: fix double put of gadget device on setup failure Anfernee Cao
2026-10-20 14:31 ` sashiko-bot [this message]
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=sashiko-outbox-179144@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=anferneemelokc5@gmail.com \
--cc=linux-usb@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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