From: patchwork-bot+netdevbpf@kernel.org
To: Wei Yongjun <weiyongjun1@huawei.com>
Cc: krzysztof.kozlowski@canonical.com, davem@davemloft.net,
kuba@kernel.org, christophe.ricard@gmail.com,
sameo@linux.intel.com, netdev@vger.kernel.org, hulkci@huawei.com
Subject: Re: [PATCH net] NFC: st21nfca: Fix memory leak in device probe and remove
Date: Tue, 28 Dec 2021 12:50:09 +0000 [thread overview]
Message-ID: <164069580981.6060.173027739512573206.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211228124811.3122182-1-weiyongjun1@huawei.com>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Tue, 28 Dec 2021 12:48:11 +0000 you wrote:
> 'phy->pending_skb' is alloced when device probe, but forgot to free
> in the error handling path and remove path, this cause memory leak
> as follows:
>
> unreferenced object 0xffff88800bc06800 (size 512):
> comm "8", pid 11775, jiffies 4295159829 (age 9.032s)
> hex dump (first 32 bytes):
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> backtrace:
> [<00000000d66c09ce>] __kmalloc_node_track_caller+0x1ed/0x450
> [<00000000c93382b3>] kmalloc_reserve+0x37/0xd0
> [<000000005fea522c>] __alloc_skb+0x124/0x380
> [<0000000019f29f9a>] st21nfca_hci_i2c_probe+0x170/0x8f2
>
> [...]
Here is the summary with links:
- [net] NFC: st21nfca: Fix memory leak in device probe and remove
https://git.kernel.org/netdev/net/c/1b9dadba5022
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-12-28 12:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-28 12:48 [PATCH net] NFC: st21nfca: Fix memory leak in device probe and remove Wei Yongjun
2021-12-28 12:50 ` 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=164069580981.6060.173027739512573206.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=christophe.ricard@gmail.com \
--cc=davem@davemloft.net \
--cc=hulkci@huawei.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sameo@linux.intel.com \
--cc=weiyongjun1@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 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.