From: patchwork-bot+netdevbpf@kernel.org
To: Chengyang Fan <cy.fan@huawei.com>
Cc: davem@davemloft.net, yoshfuji@linux-ipv6.org, dsahern@kernel.org,
kuba@kernel.org, liuhangbin@gmail.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: ipv4: fix memory leak in ip_mc_add1_src
Date: Wed, 16 Jun 2021 19:50:04 +0000 [thread overview]
Message-ID: <162387300488.13042.4367542088797700653.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210616095925.1571600-1-cy.fan@huawei.com>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Wed, 16 Jun 2021 17:59:25 +0800 you wrote:
> BUG: memory leak
> unreferenced object 0xffff888101bc4c00 (size 32):
> comm "syz-executor527", pid 360, jiffies 4294807421 (age 19.329s)
> hex dump (first 32 bytes):
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> 01 00 00 00 00 00 00 00 ac 14 14 bb 00 00 02 00 ................
> backtrace:
> [<00000000f17c5244>] kmalloc include/linux/slab.h:558 [inline]
> [<00000000f17c5244>] kzalloc include/linux/slab.h:688 [inline]
> [<00000000f17c5244>] ip_mc_add1_src net/ipv4/igmp.c:1971 [inline]
> [<00000000f17c5244>] ip_mc_add_src+0x95f/0xdb0 net/ipv4/igmp.c:2095
> [<000000001cb99709>] ip_mc_source+0x84c/0xea0 net/ipv4/igmp.c:2416
> [<0000000052cf19ed>] do_ip_setsockopt net/ipv4/ip_sockglue.c:1294 [inline]
> [<0000000052cf19ed>] ip_setsockopt+0x114b/0x30c0 net/ipv4/ip_sockglue.c:1423
> [<00000000477edfbc>] raw_setsockopt+0x13d/0x170 net/ipv4/raw.c:857
> [<00000000e75ca9bb>] __sys_setsockopt+0x158/0x270 net/socket.c:2117
> [<00000000bdb993a8>] __do_sys_setsockopt net/socket.c:2128 [inline]
> [<00000000bdb993a8>] __se_sys_setsockopt net/socket.c:2125 [inline]
> [<00000000bdb993a8>] __x64_sys_setsockopt+0xba/0x150 net/socket.c:2125
> [<000000006a1ffdbd>] do_syscall_64+0x40/0x80 arch/x86/entry/common.c:47
> [<00000000b11467c4>] entry_SYSCALL_64_after_hwframe+0x44/0xae
>
> [...]
Here is the summary with links:
- net: ipv4: fix memory leak in ip_mc_add1_src
https://git.kernel.org/netdev/net/c/d8e2973029b8
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-06-16 19:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 9:59 [PATCH] net: ipv4: fix memory leak in ip_mc_add1_src Chengyang Fan
2021-06-16 11:52 ` Hangbin Liu
2021-06-16 19: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=162387300488.13042.4367542088797700653.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=cy.fan@huawei.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuhangbin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.org \
/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).