Hello, syzbot found the following issue on:
HEAD commit: 13391c60 Merge branch 'linus' of git://git.kernel.org/pub/.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=15eb761b500000 kernel config: https://syzkaller.appspot.com/x/.config?x=e7e6ee96c9292f22 dashboard link: https://syzkaller.appspot.com/bug?extid=35a511c72ea7356cdcf3 compiler: gcc (GCC) 10.1.0-syz 20200507 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=103c58a0d00000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1040bc54d00000 IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+35a511c72ea7356cd...@syzkaller.appspotmail.com Warning: Permanently added '10.128.0.186' (ECDSA) to the list of known hosts. executing program executing program BUG: memory leak unreferenced object 0xffff88810127da40 (size 824): comm "syz-executor472", pid 8431, jiffies 4294942269 (age 13.980s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 2a 00 01 40 00 00 00 00 00 00 00 00 00 00 00 00 *..@............ backtrace: [<0000000041c0b1fe>] sk_prot_alloc+0x3e/0x1c0 net/core/sock.c:1679 [<00000000f73c2f2d>] sk_alloc+0x30/0x3f0 net/core/sock.c:1739 [<0000000069049cba>] qrtr_create+0x4d/0xb0 net/qrtr/qrtr.c:1258 [<0000000077afae5e>] __sock_create+0x1ab/0x2b0 net/socket.c:1406 [<000000007f58f353>] sock_create net/socket.c:1457 [inline] [<000000007f58f353>] __sys_socket+0x6f/0x140 net/socket.c:1499 [<00000000217ba93a>] __do_sys_socket net/socket.c:1508 [inline] [<00000000217ba93a>] __se_sys_socket net/socket.c:1506 [inline] [<00000000217ba93a>] __x64_sys_socket+0x1a/0x20 net/socket.c:1506 [<00000000632eec5e>] do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46 [<00000000a6403a3c>] entry_SYSCALL_64_after_hwframe+0x44/0xa9 --- This report is generated by a bot. It may contain errors. See https://goo.gl/tpsmEJ for more information about syzbot. syzbot engineers can be reached at syzkal...@googlegroups.com. syzbot will keep track of this issue. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot. syzbot can test patches for this issue, for details see: https://goo.gl/tpsmEJ#testing-patches
