From: Eric Biggers <ebiggers@kernel.org>
To: cH3332 XR <ch3332xr@gmail.com>
Cc: linux-mm@kvack.org, syzkaller@googlegroups.com
Subject: Re: memory leak in ip_mc_add_src ( Not tainted 5.8.0-rc3+)
Date: Thu, 9 Jul 2020 23:28:25 -0700 [thread overview]
Message-ID: <20200710062825.GC2805@sol.localdomain> (raw)
In-Reply-To: <CAJ5WPnHxmanrgV0jKRiZt42YAA-H-_3HBC9LpPrYmgAcaxA5jw@mail.gmail.com>
On Fri, Jul 10, 2020 at 11:47:07AM +0530, cH3332 XR wrote:
> Hi,
> SYZKALLER found the following Memory leak
>
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> BUG: memory leak
> unreferenced object 0xffff955412ff9e00 (size 32):
> comm "syz-executor.3", pid 4726, jiffies 4294777846 (age 3098.168s)
> hex dump (first 32 bytes):
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> 06 00 00 00 00 00 00 00 ac 1e 00 04 00 00 00 00 ................
> backtrace:
> [<000000002976d53e>] ip_mc_add_src+0x35f/0x3e0
> [<00000000f22fc984>] ip_mc_source+0x2db/0x4e0
> [<00000000a814b668>] do_ip_setsockopt.isra.14+0x541/0x11c0
> [<0000000071f25adf>] ip_setsockopt+0x33/0xa0
> [<00000000a49ec12e>] udp_setsockopt+0x40/0x90
> [<000000002cc8a42f>] __sys_setsockopt+0x99/0x120
> [<00000000167d1a29>] __x64_sys_setsockopt+0x22/0x30
> [<00000000971d38a0>] do_syscall_64+0x3e/0x70
> [<00000000b19407da>] entry_SYSCALL_64_after_hwframe+0x44/0xa9
This looks like a bug in networking code, so you'd probably have better luck
sending this to netdev@vger.kernel.org instead of linux-mm@kvack.org. Also if
you can please send a patch.
- Eric
prev parent reply other threads:[~2020-07-10 6:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-10 6:17 memory leak in ip_mc_add_src ( Not tainted 5.8.0-rc3+) cH3332 XR
2020-07-10 6:28 ` Eric Biggers [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=20200710062825.GC2805@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=ch3332xr@gmail.com \
--cc=linux-mm@kvack.org \
--cc=syzkaller@googlegroups.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).