From: patchwork-bot+netdevbpf@kernel.org
To: Nanyong Sun <sunnanyong@huawei.com>
Cc: paul@paul-moore.com, davem@davemloft.net,
yoshfuji@linux-ipv6.org, dsahern@kernel.org, kuba@kernel.org,
netdev@vger.kernel.org, linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: ipv4: fix memory leak in netlbl_cipsov4_add_std
Date: Tue, 08 Jun 2021 18:40:04 +0000 [thread overview]
Message-ID: <162317760423.20688.10311638397902674413.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210608015158.3848878-1-sunnanyong@huawei.com>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Tue, 8 Jun 2021 09:51:58 +0800 you wrote:
> Reported by syzkaller:
> BUG: memory leak
> unreferenced object 0xffff888105df7000 (size 64):
> comm "syz-executor842", pid 360, jiffies 4294824824 (age 22.546s)
> hex dump (first 32 bytes):
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> backtrace:
> [<00000000e67ed558>] kmalloc include/linux/slab.h:590 [inline]
> [<00000000e67ed558>] kzalloc include/linux/slab.h:720 [inline]
> [<00000000e67ed558>] netlbl_cipsov4_add_std net/netlabel/netlabel_cipso_v4.c:145 [inline]
> [<00000000e67ed558>] netlbl_cipsov4_add+0x390/0x2340 net/netlabel/netlabel_cipso_v4.c:416
> [<0000000006040154>] genl_family_rcv_msg_doit.isra.0+0x20e/0x320 net/netlink/genetlink.c:739
> [<00000000204d7a1c>] genl_family_rcv_msg net/netlink/genetlink.c:783 [inline]
> [<00000000204d7a1c>] genl_rcv_msg+0x2bf/0x4f0 net/netlink/genetlink.c:800
> [<00000000c0d6a995>] netlink_rcv_skb+0x134/0x3d0 net/netlink/af_netlink.c:2504
> [<00000000d78b9d2c>] genl_rcv+0x24/0x40 net/netlink/genetlink.c:811
> [<000000009733081b>] netlink_unicast_kernel net/netlink/af_netlink.c:1314 [inline]
> [<000000009733081b>] netlink_unicast+0x4a0/0x6a0 net/netlink/af_netlink.c:1340
> [<00000000d5fd43b8>] netlink_sendmsg+0x789/0xc70 net/netlink/af_netlink.c:1929
> [<000000000a2d1e40>] sock_sendmsg_nosec net/socket.c:654 [inline]
> [<000000000a2d1e40>] sock_sendmsg+0x139/0x170 net/socket.c:674
> [<00000000321d1969>] ____sys_sendmsg+0x658/0x7d0 net/socket.c:2350
> [<00000000964e16bc>] ___sys_sendmsg+0xf8/0x170 net/socket.c:2404
> [<000000001615e288>] __sys_sendmsg+0xd3/0x190 net/socket.c:2433
> [<000000004ee8b6a5>] do_syscall_64+0x37/0x90 arch/x86/entry/common.c:47
> [<00000000171c7cee>] entry_SYSCALL_64_after_hwframe+0x44/0xae
>
> [...]
Here is the summary with links:
- net: ipv4: fix memory leak in netlbl_cipsov4_add_std
https://git.kernel.org/netdev/net/c/d612c3f3fae2
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-08 18:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 1:51 [PATCH] net: ipv4: fix memory leak in netlbl_cipsov4_add_std Nanyong Sun
2021-06-08 1:53 ` Paul Moore
2021-06-08 2:30 ` Dongliang Mu
2021-06-08 2:56 ` Dongliang Mu
2021-06-08 2:56 ` Paul Moore
2021-06-08 18: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=162317760423.20688.10311638397902674413.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=sunnanyong@huawei.com \
--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).