From: patchwork-bot+netdevbpf@kernel.org
To: Yang Yingliang <yangyingliang@huawei.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
davem@davemloft.net, kuba@kernel.org
Subject: Re: [PATCH net] net/802/mrp: fix memleak in mrp_request_join()
Date: Thu, 01 Jul 2021 18:20:04 +0000 [thread overview]
Message-ID: <162516360421.12749.14576932158898469827.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210629072237.991461-1-yangyingliang@huawei.com>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Tue, 29 Jun 2021 15:22:37 +0800 you wrote:
> I got kmemleak report when doing fuzz test:
>
> BUG: memory leak
> unreferenced object 0xffff88810c239500 (size 64):
> comm "syz-executor940", pid 882, jiffies 4294712870 (age 14.631s)
> hex dump (first 32 bytes):
> 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> 00 00 00 00 00 00 00 00 01 00 00 00 01 02 00 04 ................
> backtrace:
> [<00000000a323afa4>] slab_alloc_node mm/slub.c:2972 [inline]
> [<00000000a323afa4>] slab_alloc mm/slub.c:2980 [inline]
> [<00000000a323afa4>] __kmalloc+0x167/0x340 mm/slub.c:4130
> [<000000005034ca11>] kmalloc include/linux/slab.h:595 [inline]
> [<000000005034ca11>] mrp_attr_create net/802/mrp.c:276 [inline]
> [<000000005034ca11>] mrp_request_join+0x265/0x550 net/802/mrp.c:530
> [<00000000fcfd81f3>] vlan_mvrp_request_join+0x145/0x170 net/8021q/vlan_mvrp.c:40
> [<000000009258546e>] vlan_dev_open+0x477/0x890 net/8021q/vlan_dev.c:292
> [<0000000059acd82b>] __dev_open+0x281/0x410 net/core/dev.c:1609
> [<000000004e6dc695>] __dev_change_flags+0x424/0x560 net/core/dev.c:8767
> [<00000000471a09af>] rtnl_configure_link+0xd9/0x210 net/core/rtnetlink.c:3122
> [<0000000037a4672b>] __rtnl_newlink+0xe08/0x13e0 net/core/rtnetlink.c:3448
> [<000000008d5d0fda>] rtnl_newlink+0x64/0xa0 net/core/rtnetlink.c:3488
> [<000000004882fe39>] rtnetlink_rcv_msg+0x369/0xa10 net/core/rtnetlink.c:5552
> [<00000000907e6c54>] netlink_rcv_skb+0x134/0x3d0 net/netlink/af_netlink.c:2504
> [<00000000e7d7a8c4>] netlink_unicast_kernel net/netlink/af_netlink.c:1314 [inline]
> [<00000000e7d7a8c4>] netlink_unicast+0x4a0/0x6a0 net/netlink/af_netlink.c:1340
> [<00000000e0645d50>] netlink_sendmsg+0x78e/0xc90 net/netlink/af_netlink.c:1929
> [<00000000c24559b7>] sock_sendmsg_nosec net/socket.c:654 [inline]
> [<00000000c24559b7>] sock_sendmsg+0x139/0x170 net/socket.c:674
> [<00000000fc210bc2>] ____sys_sendmsg+0x658/0x7d0 net/socket.c:2350
> [<00000000be4577b5>] ___sys_sendmsg+0xf8/0x170 net/socket.c:2404
>
> [...]
Here is the summary with links:
- [net] net/802/mrp: fix memleak in mrp_request_join()
https://git.kernel.org/netdev/net/c/996af62167d0
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-07-01 18:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 7:22 [PATCH net] net/802/mrp: fix memleak in mrp_request_join() Yang Yingliang
2021-07-01 18:20 ` 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=162516360421.12749.14576932158898469827.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yangyingliang@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 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).