From: Peter Korsgaard <peter@korsgaard.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Ming Qing <a0yami@mailbox.org>,
linux-usb@vger.kernel.org, julian@jusst.de,
Pavel Hofman <pavel.hofman@ivitera.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] usb: gadget: f_uac2: fix memory leak in UAC2_RATE_ATTRIBUTE store
Date: Wed, 15 Jul 2026 11:57:52 +0200 [thread overview]
Message-ID: <87ldbc7exr.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <2026071044-goggles-preview-5a9c@gregkh> (Greg KH's message of "Fri, 10 Jul 2026 14:56:59 +0200")
>>>>> "Greg" == Greg KH <gregkh@linuxfoundation.org> writes:
> On Mon, Jun 15, 2026 at 06:52:01PM +0800, Ming Qing wrote:
>> On Sun, Jun 14, 2026 at 5:39 PM +0800, Peter Korsgaard wrote:
>> > FYI, I see the same issue is also fixed in the recently proposed
>> > "[PATCH] usb: gadget: uac: validate rate list length before storing"
>> >
>> > https://lore.kernel.org/linux-usb/20260519143319.147494-1-a0yami@mailbox.org/
>>
>> Yes, that includes the same buffer lifetime fix. I'm happy to split
>> it up if that makes it easier to pick.
>>
> Please do, I just took that one now and this series does not apply.
With "usb: gadget: uac: validate rate list length before storing"
applied, these two patches are afaik no longer needed as that patch also
fixes the same leak.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2026-07-15 9:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 9:19 [PATCH 1/2] usb: gadget: f_uac2: fix memory leak in UAC2_RATE_ATTRIBUTE store Peter Korsgaard
2026-06-09 9:19 ` [PATCH 2/2] usb: gadget: f_uac1: fix memory leak in UAC1_RATE_ATTRIBUTE store Peter Korsgaard
2026-06-14 9:39 ` [PATCH 1/2] usb: gadget: f_uac2: fix memory leak in UAC2_RATE_ATTRIBUTE store Peter Korsgaard
2026-06-15 10:52 ` Ming Qing
2026-07-10 12:56 ` Greg KH
2026-07-15 9:57 ` Peter Korsgaard [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=87ldbc7exr.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=a0yami@mailbox.org \
--cc=gregkh@linuxfoundation.org \
--cc=julian@jusst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=pavel.hofman@ivitera.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.