From: patchwork-bot+netdevbpf@kernel.org
To: Peilin Ye <yepeilin.cs@gmail.com>
Cc: oneukum@suse.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, peilin.ye@bytedance.com,
gregkh@linuxfoundation.org, ming.lei@canonical.com,
cong.wang@bytedance.com, netdev@vger.kernel.org,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] usbnet: Fix memory leak in usbnet_disconnect()
Date: Mon, 26 Sep 2022 18:40:14 +0000 [thread overview]
Message-ID: <166421761477.17810.9199629462308924051.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220923042551.2745-1-yepeilin.cs@gmail.com>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 22 Sep 2022 21:25:51 -0700 you wrote:
> From: Peilin Ye <peilin.ye@bytedance.com>
>
> Currently usbnet_disconnect() unanchors and frees all deferred URBs
> using usb_scuttle_anchored_urbs(), which does not free urb->context,
> causing a memory leak as reported by syzbot.
>
> Use a usb_get_from_anchor() while loop instead, similar to what we did
> in commit 19cfe912c37b ("Bluetooth: btusb: Fix memory leak in
> play_deferred"). Also free urb->sg.
>
> [...]
Here is the summary with links:
- [net] usbnet: Fix memory leak in usbnet_disconnect()
https://git.kernel.org/netdev/net/c/a43206156263
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-09-26 18:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 0:29 [syzbot] memory leak in mld_newpack syzbot
2022-09-16 22:13 ` syzbot
2022-09-23 4:25 ` [PATCH net] usbnet: Fix memory leak in usbnet_disconnect() Peilin Ye
2022-09-26 10:47 ` Oliver Neukum
2022-09-26 18:40 ` patchwork-bot+netdevbpf [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=166421761477.17810.9199629462308924051.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=cong.wang@bytedance.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=ming.lei@canonical.com \
--cc=netdev@vger.kernel.org \
--cc=oneukum@suse.com \
--cc=pabeni@redhat.com \
--cc=peilin.ye@bytedance.com \
--cc=yepeilin.cs@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 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).