From: patchwork-bot+netdevbpf@kernel.org
To: Wong Vee Khee <vee.khee.wong@linux.intel.com>
Cc: peppe.cavallaro@st.com, alexandre.torgue@foss.st.com,
joabreu@synopsys.com, davem@davemloft.net, kuba@kernel.org,
mcoquelin.stm32@gmail.com, boon.leong.ong@intel.com,
netdev@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 1/1] net: stmmac: fix memory leak during driver probe
Date: Mon, 19 Apr 2021 23:10:15 +0000 [thread overview]
Message-ID: <161887381539.661.5024854346370869109.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210419112530.20395-1-vee.khee.wong@linux.intel.com>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Mon, 19 Apr 2021 19:25:30 +0800 you wrote:
> On driver probe, kmemleak reported the following memory leak which was
> due to allocated bitmap that was not being freed in stmmac_dvr_probe().
>
> unreferenced object 0xffff9276014b13c0 (size 8):
> comm "systemd-udevd", pid 2143, jiffies 4294681112 (age 116.720s)
> hex dump (first 8 bytes):
> 00 00 00 00 00 00 00 00 ........
> backtrace:
> [<00000000c51e34b2>] stmmac_dvr_probe+0x1c0/0x440 [stmmac]
> [<00000000b530eb41>] intel_eth_pci_probe.cold+0x2b/0x14e [dwmac_intel]
> [<00000000b10f8929>] pci_device_probe+0xd2/0x150
> [<00000000fb254c74>] really_probe+0xf8/0x410
> [<0000000034128a59>] driver_probe_device+0x5d/0x150
> [<00000000016104d5>] device_driver_attach+0x53/0x60
> [<00000000cb18cd07>] __driver_attach+0x96/0x140
> [<00000000da9ffd5c>] bus_for_each_dev+0x7a/0xc0
> [<00000000af061a88>] bus_add_driver+0x184/0x1f0
> [<000000008be5c1c5>] driver_register+0x6c/0xc0
> [<0000000052b18a9e>] do_one_initcall+0x4d/0x210
> [<00000000154d4f07>] do_init_module+0x5c/0x230
> [<000000009b648d09>] load_module+0x2a5a/0x2d40
> [<000000000d86b76d>] __do_sys_finit_module+0xb5/0x120
> [<000000002b0cef95>] do_syscall_64+0x33/0x40
> [<0000000067b45bbb>] entry_SYSCALL_64_after_hwframe+0x44/0xa9
>
> [...]
Here is the summary with links:
- [net-next,1/1] net: stmmac: fix memory leak during driver probe
https://git.kernel.org/netdev/net-next/c/d7f576dc9836
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+netdevbpf@kernel.org
To: Wong Vee Khee <vee.khee.wong@linux.intel.com>
Cc: peppe.cavallaro@st.com, alexandre.torgue@foss.st.com,
joabreu@synopsys.com, davem@davemloft.net, kuba@kernel.org,
mcoquelin.stm32@gmail.com, boon.leong.ong@intel.com,
netdev@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 1/1] net: stmmac: fix memory leak during driver probe
Date: Mon, 19 Apr 2021 23:10:15 +0000 [thread overview]
Message-ID: <161887381539.661.5024854346370869109.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210419112530.20395-1-vee.khee.wong@linux.intel.com>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Mon, 19 Apr 2021 19:25:30 +0800 you wrote:
> On driver probe, kmemleak reported the following memory leak which was
> due to allocated bitmap that was not being freed in stmmac_dvr_probe().
>
> unreferenced object 0xffff9276014b13c0 (size 8):
> comm "systemd-udevd", pid 2143, jiffies 4294681112 (age 116.720s)
> hex dump (first 8 bytes):
> 00 00 00 00 00 00 00 00 ........
> backtrace:
> [<00000000c51e34b2>] stmmac_dvr_probe+0x1c0/0x440 [stmmac]
> [<00000000b530eb41>] intel_eth_pci_probe.cold+0x2b/0x14e [dwmac_intel]
> [<00000000b10f8929>] pci_device_probe+0xd2/0x150
> [<00000000fb254c74>] really_probe+0xf8/0x410
> [<0000000034128a59>] driver_probe_device+0x5d/0x150
> [<00000000016104d5>] device_driver_attach+0x53/0x60
> [<00000000cb18cd07>] __driver_attach+0x96/0x140
> [<00000000da9ffd5c>] bus_for_each_dev+0x7a/0xc0
> [<00000000af061a88>] bus_add_driver+0x184/0x1f0
> [<000000008be5c1c5>] driver_register+0x6c/0xc0
> [<0000000052b18a9e>] do_one_initcall+0x4d/0x210
> [<00000000154d4f07>] do_init_module+0x5c/0x230
> [<000000009b648d09>] load_module+0x2a5a/0x2d40
> [<000000000d86b76d>] __do_sys_finit_module+0xb5/0x120
> [<000000002b0cef95>] do_syscall_64+0x33/0x40
> [<0000000067b45bbb>] entry_SYSCALL_64_after_hwframe+0x44/0xa9
>
> [...]
Here is the summary with links:
- [net-next,1/1] net: stmmac: fix memory leak during driver probe
https://git.kernel.org/netdev/net-next/c/d7f576dc9836
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-04-19 23:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-19 11:25 [PATCH net-next 1/1] net: stmmac: fix memory leak during driver probe Wong Vee Khee
2021-04-19 11:25 ` Wong Vee Khee
2021-04-19 23:10 ` patchwork-bot+netdevbpf [this message]
2021-04-19 23:10 ` patchwork-bot+netdevbpf
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=161887381539.661.5024854346370869109.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=boon.leong.ong@intel.com \
--cc=davem@davemloft.net \
--cc=joabreu@synopsys.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.com \
--cc=vee.khee.wong@linux.intel.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.