From: Oliver Neukum <oneukum@suse.com>
To: Takashi Iwai <tiwai@suse.de>, Oliver Neukum <oneukum@suse.com>
Cc: syzbot+2afd7e71155c7e241560@syzkaller.appspotmail.com,
linux-usb@vger.kernel.org, tiwai@suse.com
Subject: Re: [PATCH] sound: usb: caiaq: fix reference leak in probe error
Date: Wed, 29 Apr 2026 13:05:47 +0200 [thread overview]
Message-ID: <53355559-faa9-4386-b6f4-390fb1409ef3@suse.com> (raw)
In-Reply-To: <87se8eox4r.wl-tiwai@suse.de>
On 29.04.26 12:53, Takashi Iwai wrote:
> On Wed, 29 Apr 2026 12:45:24 +0200,
> Oliver Neukum wrote:
>>
>> If probing a device fails early a reference to a device
>> is leaked.
>>
>> Signed-off-by: Oliver Neukum <oneukum@suse.com>
>
> Thanks, but I believe it's been already fixed in my tree for 7.1-rc2:
> 7a5f1cd22d47f8ca4b760b6334378ae42c1bd24b
> ALSA: caiaq: fix usb_dev refcount leak on probe failure
>
> Also, there are a couple of fixes for caiaq queued for 7.1-rc2, too.
Very good. Such things happen.
Regards
Oliver
next prev parent reply other threads:[~2026-04-29 11:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-25 2:12 [syzbot] [usb?] memory leak in hub_event (4) syzbot
2026-04-27 11:40 ` Oliver Neukum
2026-04-27 12:37 ` syzbot
2026-04-27 14:19 ` Alan Stern
2026-04-28 11:33 ` Oliver Neukum
2026-04-28 15:12 ` Alan Stern
2026-04-29 10:42 ` [PATCH] usb: core: hcd: fix possible deadlock in rh control transfers Oliver Neukum
2026-04-29 19:04 ` Alan Stern
2026-04-29 19:13 ` Oliver Neukum
2026-04-29 19:18 ` Alan Stern
2026-04-29 10:45 ` [PATCH] sound: usb: caiaq: fix reference leak in probe error Oliver Neukum
2026-04-29 10:53 ` Takashi Iwai
2026-04-29 11:05 ` Oliver Neukum [this message]
2026-04-29 19:42 ` kernel test robot
2026-04-30 5:33 ` kernel test robot
2026-04-30 11:02 ` kernel test robot
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=53355559-faa9-4386-b6f4-390fb1409ef3@suse.com \
--to=oneukum@suse.com \
--cc=linux-usb@vger.kernel.org \
--cc=syzbot+2afd7e71155c7e241560@syzkaller.appspotmail.com \
--cc=tiwai@suse.com \
--cc=tiwai@suse.de \
/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