From: patchwork-bot+netdevbpf@kernel.org
To: Chen Zhongjin <chenzhongjin@huawei.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
andrew@lunn.ch, vivien.didelot@gmail.com, f.fainelli@gmail.com,
olteanv@gmail.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com
Subject: Re: [PATCH] net: dsa: Fix possible memory leaks in dsa_loop_init()
Date: Fri, 28 Oct 2022 09:40:14 +0000 [thread overview]
Message-ID: <166695001475.8410.5727114306921032694.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221026020321.58615-1-chenzhongjin@huawei.com>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Wed, 26 Oct 2022 10:03:21 +0800 you wrote:
> kmemleak reported memory leaks in dsa_loop_init():
>
> kmemleak: 12 new suspected memory leaks
>
> unreferenced object 0xffff8880138ce000 (size 2048):
> comm "modprobe", pid 390, jiffies 4295040478 (age 238.976s)
> backtrace:
> [<000000006a94f1d5>] kmalloc_trace+0x26/0x60
> [<00000000a9c44622>] phy_device_create+0x5d/0x970
> [<00000000d0ee2afc>] get_phy_device+0xf3/0x2b0
> [<00000000dca0c71f>] __fixed_phy_register.part.0+0x92/0x4e0
> [<000000008a834798>] fixed_phy_register+0x84/0xb0
> [<0000000055223fcb>] dsa_loop_init+0xa9/0x116 [dsa_loop]
> ...
>
> [...]
Here is the summary with links:
- net: dsa: Fix possible memory leaks in dsa_loop_init()
https://git.kernel.org/netdev/net/c/633efc8b3dc9
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-10-28 9:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 2:03 [PATCH] net: dsa: Fix possible memory leaks in dsa_loop_init() Chen Zhongjin
2022-10-28 9: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=166695001475.8410.5727114306921032694.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=chenzhongjin@huawei.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=vivien.didelot@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