From: syzbot <syzbot+06537213db7ba2745c4a@syzkaller.appspotmail.com>
To: aviadye@mellanox.com, borisp@mellanox.com, daniel@iogearbox.net,
davejwatson@fb.com, davem@davemloft.net,
john.fastabend@gmail.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: memory leak in create_ctx
Date: Sat, 08 Jun 2019 12:13:06 -0700 [thread overview]
Message-ID: <000000000000a420af058ad4bca2@google.com> (raw)
Hello,
syzbot found the following crash on:
HEAD commit: 79c3ba32 Merge tag 'drm-fixes-2019-06-07-1' of git://anong..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=170e0bfea00000
kernel config: https://syzkaller.appspot.com/x/.config?x=d5c73825cbdc7326
dashboard link: https://syzkaller.appspot.com/bug?extid=06537213db7ba2745c4a
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10aa806aa00000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+06537213db7ba2745c4a@syzkaller.appspotmail.com
IPv6: ADDRCONF(NETDEV_CHANGE): team0: link becomes ready
2019/06/08 14:55:51 executed programs: 15
2019/06/08 14:55:56 executed programs: 31
2019/06/08 14:56:02 executed programs: 51
BUG: memory leak
unreferenced object 0xffff888117ceae00 (size 512):
comm "syz-executor.3", pid 7233, jiffies 4294949016 (age 13.640s)
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:
[<00000000e6550967>] kmemleak_alloc_recursive
include/linux/kmemleak.h:55 [inline]
[<00000000e6550967>] slab_post_alloc_hook mm/slab.h:439 [inline]
[<00000000e6550967>] slab_alloc mm/slab.c:3326 [inline]
[<00000000e6550967>] kmem_cache_alloc_trace+0x13d/0x280 mm/slab.c:3553
[<0000000014132182>] kmalloc include/linux/slab.h:547 [inline]
[<0000000014132182>] kzalloc include/linux/slab.h:742 [inline]
[<0000000014132182>] create_ctx+0x25/0x70 net/tls/tls_main.c:601
[<00000000e08e1a44>] tls_init net/tls/tls_main.c:787 [inline]
[<00000000e08e1a44>] tls_init+0x97/0x1e0 net/tls/tls_main.c:769
[<0000000037b0c43c>] __tcp_set_ulp net/ipv4/tcp_ulp.c:126 [inline]
[<0000000037b0c43c>] tcp_set_ulp+0xe2/0x190 net/ipv4/tcp_ulp.c:147
[<000000007a284277>] do_tcp_setsockopt.isra.0+0x19a/0xd60
net/ipv4/tcp.c:2784
[<00000000f35f3415>] tcp_setsockopt+0x71/0x80 net/ipv4/tcp.c:3098
[<00000000c840962c>] sock_common_setsockopt+0x38/0x50
net/core/sock.c:3124
[<0000000006b0801f>] __sys_setsockopt+0x98/0x120 net/socket.c:2072
[<00000000a6309f52>] __do_sys_setsockopt net/socket.c:2083 [inline]
[<00000000a6309f52>] __se_sys_setsockopt net/socket.c:2080 [inline]
[<00000000a6309f52>] __x64_sys_setsockopt+0x26/0x30 net/socket.c:2080
[<00000000fa555bbc>] do_syscall_64+0x76/0x1a0
arch/x86/entry/common.c:301
[<00000000a06d7d1a>] entry_SYSCALL_64_after_hwframe+0x44/0xa9
BUG: memory leak
unreferenced object 0xffff88810965dc00 (size 512):
comm "syz-executor.2", pid 7235, jiffies 4294949016 (age 13.640s)
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:
[<00000000e6550967>] kmemleak_alloc_recursive
include/linux/kmemleak.h:55 [inline]
[<00000000e6550967>] slab_post_alloc_hook mm/slab.h:439 [inline]
[<00000000e6550967>] slab_alloc mm/slab.c:3326 [inline]
[<00000000e6550967>] kmem_cache_alloc_trace+0x13d/0x280 mm/slab.c:3553
[<0000000014132182>] kmalloc include/linux/slab.h:547 [inline]
[<0000000014132182>] kzalloc include/linux/slab.h:742 [inline]
[<0000000014132182>] create_ctx+0x25/0x70 net/tls/tls_main.c:601
[<00000000e08e1a44>] tls_init net/tls/tls_main.c:787 [inline]
[<00000000e08e1a44>] tls_init+0x97/0x1e0 net/tls/tls_main.c:769
[<0000000037b0c43c>] __tcp_set_ulp net/ipv4/tcp_ulp.c:126 [inline]
[<0000000037b0c43c>] tcp_set_ulp+0xe2/0x190 net/ipv4/tcp_ulp.c:147
[<000000007a284277>] do_tcp_setsockopt.isra.0+0x19a/0xd60
net/ipv4/tcp.c:2784
[<00000000f35f3415>] tcp_setsockopt+0x71/0x80 net/ipv4/tcp.c:3098
[<00000000c840962c>] sock_common_setsockopt+0x38/0x50
net/core/sock.c:3124
[<0000000006b0801f>] __sys_setsockopt+0x98/0x120 net/socket.c:2072
[<00000000a6309f52>] __do_sys_setsockopt net/socket.c:2083 [inline]
[<00000000a6309f52>] __se_sys_setsockopt net/socket.c:2080 [inline]
[<00000000a6309f52>] __x64_sys_setsockopt+0x26/0x30 net/socket.c:2080
[<00000000fa555bbc>] do_syscall_64+0x76/0x1a0
arch/x86/entry/common.c:301
[<00000000a06d7d1a>] entry_SYSCALL_64_after_hwframe+0x44/0xa9
BUG: memory leak
unreferenced object 0xffff8881207d7600 (size 512):
comm "syz-executor.5", pid 7244, jiffies 4294949019 (age 13.610s)
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:
[<00000000e6550967>] kmemleak_alloc_recursive
include/linux/kmemleak.h:55 [inline]
[<00000000e6550967>] slab_post_alloc_hook mm/slab.h:439 [inline]
[<00000000e6550967>] slab_alloc mm/slab.c:3326 [inline]
[<00000000e6550967>] kmem_cache_alloc_trace+0x13d/0x280 mm/slab.c:3553
[<0000000014132182>] kmalloc include/linux/slab.h:547 [inline]
[<0000000014132182>] kzalloc include/linux/slab.h:742 [inline]
[<0000000014132182>] create_ctx+0x25/0x70 net/tls/tls_main.c:601
[<00000000e08e1a44>] tls_init net/tls/tls_main.c:787 [inline]
[<00000000e08e1a44>] tls_init+0x97/0x1e0 net/tls/tls_main.c:769
[<0000000037b0c43c>] __tcp_set_ulp net/ipv4/tcp_ulp.c:126 [inline]
[<0000000037b0c43c>] tcp_set_ulp+0xe2/0x190 net/ipv4/tcp_ulp.c:147
[<000000007a284277>] do_tcp_setsockopt.isra.0+0x19a/0xd60
net/ipv4/tcp.c:2784
[<00000000f35f3415>] tcp_setsockopt+0x71/0x80 net/ipv4/tcp.c:3098
[<00000000c840962c>] sock_common_setsockopt+0x38/0x50
net/core/sock.c:3124
[<0000000006b0801f>] __sys_setsockopt+0x98/0x120 net/socket.c:2072
[<00000000a6309f52>] __do_sys_setsockopt net/socket.c:2083 [inline]
[<00000000a6309f52>] __se_sys_setsockopt net/socket.c:2080 [inline]
[<00000000a6309f52>] __x64_sys_setsockopt+0x26/0x30 net/socket.c:2080
[<00000000fa555bbc>] do_syscall_64+0x76/0x1a0
arch/x86/entry/common.c:301
[<00000000a06d7d1a>] entry_SYSCALL_64_after_hwframe+0x44/0xa9
---
This bug 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 syzkaller@googlegroups.com.
syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this bug, for details see:
https://goo.gl/tpsmEJ#testing-patches
next reply other threads:[~2019-06-08 19:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-08 19:13 syzbot [this message]
2019-06-08 23:47 ` memory leak in create_ctx Jakub Kicinski
2019-06-10 20:59 ` [net/tls] " Eric Biggers
2019-07-01 5:28 ` John Fastabend
2019-07-01 5:40 ` syzbot
[not found] <20190609025641.11448-1-hdanton@sina.com>
2019-06-11 11:45 ` Dmitry Vyukov
2019-06-11 17:16 ` Jakub Kicinski
[not found] <20190612045828.10212-1-hdanton@sina.com>
2019-06-14 4:21 ` John Fastabend
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=000000000000a420af058ad4bca2@google.com \
--to=syzbot+06537213db7ba2745c4a@syzkaller.appspotmail.com \
--cc=aviadye@mellanox.com \
--cc=borisp@mellanox.com \
--cc=daniel@iogearbox.net \
--cc=davejwatson@fb.com \
--cc=davem@davemloft.net \
--cc=john.fastabend@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@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).