From: patchwork-bot+netdevbpf@kernel.org
To: Pavel Skripkin <paskripkin@gmail.com>
Cc: wg@grandegger.com, mkl@pengutronix.de, davem@davemloft.net,
kuba@kernel.org, mailhol.vincent@wanadoo.fr,
linux-can@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
syzbot+91adee8d9ebb9193d22d@syzkaller.appspotmail.com
Subject: Re: [PATCH] drivers: net: fix memory leak in peak_usb_create_dev
Date: Thu, 01 Apr 2021 23:00:08 +0000 [thread overview]
Message-ID: <161731800838.8028.10693283331125703609.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210401132752.25358-1-paskripkin@gmail.com>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Thu, 1 Apr 2021 16:27:52 +0300 you wrote:
> syzbot reported memory leak in peak_usb.
> The problem was in case of failure after calling
> ->dev_init()[2] in peak_usb_create_dev()[1]. The data
> allocated int dev_init() wasn't freed, so simple
> ->dev_free() call fix this problem.
>
> backtrace:
> [<0000000079d6542a>] kmalloc include/linux/slab.h:552 [inline]
> [<0000000079d6542a>] kzalloc include/linux/slab.h:682 [inline]
> [<0000000079d6542a>] pcan_usb_fd_init+0x156/0x210 drivers/net/can/usb/peak_usb/pcan_usb_fd.c:868 [2]
> [<00000000c09f9057>] peak_usb_create_dev drivers/net/can/usb/peak_usb/pcan_usb_core.c:851 [inline] [1]
> [<00000000c09f9057>] peak_usb_probe+0x389/0x490 drivers/net/can/usb/peak_usb/pcan_usb_core.c:949
>
> [...]
Here is the summary with links:
- drivers: net: fix memory leak in peak_usb_create_dev
https://git.kernel.org/netdev/net/c/a0b96b4a6274
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:[~2021-04-01 23:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 13:27 [PATCH] drivers: net: fix memory leak in peak_usb_create_dev Pavel Skripkin
2021-04-01 23:00 ` 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=161731800838.8028.10693283331125703609.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mailhol.vincent@wanadoo.fr \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=paskripkin@gmail.com \
--cc=syzbot+91adee8d9ebb9193d22d@syzkaller.appspotmail.com \
--cc=wg@grandegger.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).