From: Kalle Valo <kvalo@codeaurora.org>
To: Navid Emamdoost <navid.emamdoost@gmail.com>
Cc: "Arend van Spriel" <arend@broadcom.com>,
"Franky Lin" <franky.lin@broadcom.com>,
"Hante Meuleman" <hante.meuleman@broadcom.com>,
"Chi-Hsien Lin" <chi-hsien.lin@cypress.com>,
"Wright Feng" <wright.feng@cypress.com>,
"David S. Miller" <davem@davemloft.net>,
"Alwin Beukers" <alwin@broadcom.com>,
"Pieter-Paul Giesberts" <pieterpg@broadcom.com>,
"Kan Yan" <kanyan@broadcom.com>,
"Franky (Zhenhui) Lin" <frankyl@broadcom.com>,
"Piotr Figiel" <p.figiel@camlintechnologies.com>,
"Rafał Miłecki" <rafal@milecki.pl>,
YueHaibing <yuehaibing@huawei.com>, "Kangjie Lu" <kjlu@umn.edu>,
linux-wireless@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com,
brcm80211-dev-list@cypress.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, emamd001@umn.edu,
"Navid Emamdoost" <navid.emamdoost@gmail.com>
Subject: Re: [PATCH] brcmfmac: Fix memory leak in brcmf_usbdev_qinit
Date: Wed, 18 Dec 2019 19:08:48 +0000 (UTC) [thread overview]
Message-ID: <20191218190848.7F5CBC4479C@smtp.codeaurora.org> (raw)
In-Reply-To: <20191215015117.21801-1-navid.emamdoost@gmail.com>
Navid Emamdoost <navid.emamdoost@gmail.com> wrote:
> In the implementation of brcmf_usbdev_qinit() the allocated memory for
> reqs is leaking if usb_alloc_urb() fails. Release reqs in the error
> handling path.
>
> Fixes: 71bb244ba2fd ("brcm80211: fmac: add USB support for bcm43235/6/8 chipsets")
> Signed-off-by: Navid Emamdoost <navid.emamdoost@gmail.com>
Patch applied to wireless-drivers-next.git, thanks.
4282dc057d75 brcmfmac: Fix memory leak in brcmf_usbdev_qinit
--
https://patchwork.kernel.org/patch/11292553/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2019-12-18 19:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-15 1:51 [PATCH] brcmfmac: Fix memory leak in brcmf_usbdev_qinit Navid Emamdoost
2019-12-18 19:08 ` Kalle Valo [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=20191218190848.7F5CBC4479C@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=alwin@broadcom.com \
--cc=arend@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211-dev-list@cypress.com \
--cc=chi-hsien.lin@cypress.com \
--cc=davem@davemloft.net \
--cc=emamd001@umn.edu \
--cc=franky.lin@broadcom.com \
--cc=frankyl@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=kanyan@broadcom.com \
--cc=kjlu@umn.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=navid.emamdoost@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=p.figiel@camlintechnologies.com \
--cc=pieterpg@broadcom.com \
--cc=rafal@milecki.pl \
--cc=wright.feng@cypress.com \
--cc=yuehaibing@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).