From: patchwork-bot+netdevbpf@kernel.org
To: Li Zetao <lizetao1@huawei.com>
Cc: weiyongjun1@huawei.com, davem@davemloft.net, edumazet@google.com,
f.fainelli@gmail.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com
Subject: Re: [PATCH net v2] r6040: Fix kmemleak in probe and remove
Date: Thu, 15 Dec 2022 12:00:17 +0000 [thread overview]
Message-ID: <167110561712.17327.3063641334105199044.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221213125614.927754-1-lizetao1@huawei.com>
Hello:
This patch was applied to netdev/net.git (master)
by Paolo Abeni <pabeni@redhat.com>:
On Tue, 13 Dec 2022 20:56:14 +0800 you wrote:
> There is a memory leaks reported by kmemleak:
>
> unreferenced object 0xffff888116111000 (size 2048):
> comm "modprobe", pid 817, jiffies 4294759745 (age 76.502s)
> hex dump (first 32 bytes):
> 00 c4 0a 04 81 88 ff ff 08 10 11 16 81 88 ff ff ................
> 08 10 11 16 81 88 ff ff 00 00 00 00 00 00 00 00 ................
> backtrace:
> [<ffffffff815bcd82>] kmalloc_trace+0x22/0x60
> [<ffffffff827e20ee>] phy_device_create+0x4e/0x90
> [<ffffffff827e6072>] get_phy_device+0xd2/0x220
> [<ffffffff827e7844>] mdiobus_scan+0xa4/0x2e0
> [<ffffffff827e8be2>] __mdiobus_register+0x482/0x8b0
> [<ffffffffa01f5d24>] r6040_init_one+0x714/0xd2c [r6040]
> ...
>
> [...]
Here is the summary with links:
- [net,v2] r6040: Fix kmemleak in probe and remove
https://git.kernel.org/netdev/net/c/7e43039a49c2
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-12-15 12:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 10:17 [PATCH] r6040: Fix kmemleak in probe and remove Li Zetao
2022-12-13 9:29 ` Wei Yongjun
2022-12-13 12:56 ` [PATCH net v2] " Li Zetao
2022-12-14 7:14 ` Leon Romanovsky
2022-12-15 12: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=167110561712.17327.3063641334105199044.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizetao1@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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.