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@xxxxxxxxxxxxxxx instead of linux-mm@xxxxxxxxx. Also if you can please send a patch. - Eric