From: syzbot <syzbot+35bc8fe94c9f38db8320@syzkaller.appspotmail.com>
To: aviadye@mellanox.com, borisp@mellanox.com, daniel@iogearbox.net,
davejwatson@fb.com, davem@davemloft.net,
jakub.kicinski@netronome.com, john.fastabend@gmail.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: memory leak in tls_init
Date: Thu, 26 Sep 2019 18:19:09 -0700 [thread overview]
Message-ID: <00000000000047a6eb05937eaced@google.com> (raw)
Hello,
syzbot found the following crash on:
HEAD commit: f41def39 Merge tag 'ceph-for-5.4-rc1' of git://github.com/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=105b7ff9600000
kernel config: https://syzkaller.appspot.com/x/.config?x=2e29707d7d1530b3
dashboard link: https://syzkaller.appspot.com/bug?extid=35bc8fe94c9f38db8320
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=145b3419600000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+35bc8fe94c9f38db8320@syzkaller.appspotmail.com
2019/09/26 13:11:21 executed programs: 23
BUG: memory leak
unreferenced object 0xffff88810e482a00 (size 512):
comm "syz-executor.4", pid 6874, jiffies 4295090041 (age 14.090s)
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:
[<00000000e93f019a>] kmemleak_alloc_recursive
include/linux/kmemleak.h:43 [inline]
[<00000000e93f019a>] slab_post_alloc_hook mm/slab.h:586 [inline]
[<00000000e93f019a>] slab_alloc mm/slab.c:3319 [inline]
[<00000000e93f019a>] kmem_cache_alloc_trace+0x145/0x2c0 mm/slab.c:3548
[<00000000268637bd>] kmalloc include/linux/slab.h:552 [inline]
[<00000000268637bd>] kzalloc include/linux/slab.h:686 [inline]
[<00000000268637bd>] create_ctx net/tls/tls_main.c:611 [inline]
[<00000000268637bd>] tls_init net/tls/tls_main.c:794 [inline]
[<00000000268637bd>] tls_init+0xbc/0x200 net/tls/tls_main.c:773
[<00000000f52c33c5>] __tcp_set_ulp net/ipv4/tcp_ulp.c:139 [inline]
[<00000000f52c33c5>] tcp_set_ulp+0xe2/0x190 net/ipv4/tcp_ulp.c:160
[<0000000009cb49a0>] do_tcp_setsockopt.isra.0+0x1c1/0xe10
net/ipv4/tcp.c:2825
[<00000000b9d96429>] tcp_setsockopt+0x71/0x80 net/ipv4/tcp.c:3152
[<0000000038a5546c>] sock_common_setsockopt+0x38/0x50
net/core/sock.c:3142
[<00000000d945b2a0>] __sys_setsockopt+0x10f/0x220 net/socket.c:2084
[<000000003c3afaa0>] __do_sys_setsockopt net/socket.c:2100 [inline]
[<000000003c3afaa0>] __se_sys_setsockopt net/socket.c:2097 [inline]
[<000000003c3afaa0>] __x64_sys_setsockopt+0x26/0x30 net/socket.c:2097
[<00000000f7f21cbd>] do_syscall_64+0x73/0x1f0
arch/x86/entry/common.c:290
[<00000000d4c003b9>] entry_SYSCALL_64_after_hwframe+0x44/0xa9
BUG: memory leak
unreferenced object 0xffff88810e71e600 (size 512):
comm "syz-executor.4", pid 6888, jiffies 4295090060 (age 13.900s)
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:
[<00000000e93f019a>] kmemleak_alloc_recursive
include/linux/kmemleak.h:43 [inline]
[<00000000e93f019a>] slab_post_alloc_hook mm/slab.h:586 [inline]
[<00000000e93f019a>] slab_alloc mm/slab.c:3319 [inline]
[<00000000e93f019a>] kmem_cache_alloc_trace+0x145/0x2c0 mm/slab.c:3548
[<00000000268637bd>] kmalloc include/linux/slab.h:552 [inline]
[<00000000268637bd>] kzalloc include/linux/slab.h:686 [inline]
[<00000000268637bd>] create_ctx net/tls/tls_main.c:611 [inline]
[<00000000268637bd>] tls_init net/tls/tls_main.c:794 [inline]
[<00000000268637bd>] tls_init+0xbc/0x200 net/tls/tls_main.c:773
[<00000000f52c33c5>] __tcp_set_ulp net/ipv4/tcp_ulp.c:139 [inline]
[<00000000f52c33c5>] tcp_set_ulp+0xe2/0x190 net/ipv4/tcp_ulp.c:160
[<0000000009cb49a0>] do_tcp_setsockopt.isra.0+0x1c1/0xe10
net/ipv4/tcp.c:2825
[<00000000b9d96429>] tcp_setsockopt+0x71/0x80 net/ipv4/tcp.c:3152
[<0000000038a5546c>] sock_common_setsockopt+0x38/0x50
net/core/sock.c:3142
[<00000000d945b2a0>] __sys_setsockopt+0x10f/0x220 net/socket.c:2084
[<000000003c3afaa0>] __do_sys_setsockopt net/socket.c:2100 [inline]
[<000000003c3afaa0>] __se_sys_setsockopt net/socket.c:2097 [inline]
[<000000003c3afaa0>] __x64_sys_setsockopt+0x26/0x30 net/socket.c:2097
[<00000000f7f21cbd>] do_syscall_64+0x73/0x1f0
arch/x86/entry/common.c:290
[<00000000d4c003b9>] entry_SYSCALL_64_after_hwframe+0x44/0xa9
BUG: memory leak
unreferenced object 0xffff88810e356800 (size 512):
comm "syz-executor.0", pid 6926, jiffies 4295090085 (age 13.650s)
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:
[<00000000e93f019a>] kmemleak_alloc_recursive
include/linux/kmemleak.h:43 [inline]
[<00000000e93f019a>] slab_post_alloc_hook mm/slab.h:586 [inline]
[<00000000e93f019a>] slab_alloc mm/slab.c:3319 [inline]
[<00000000e93f019a>] kmem_cache_alloc_trace+0x145/0x2c0 mm/slab.c:3548
[<00000000268637bd>] kmalloc include/linux/slab.h:552 [inline]
[<00000000268637bd>] kzalloc include/linux/slab.h:686 [inline]
[<00000000268637bd>] create_ctx net/tls/tls_main.c:611 [inline]
[<00000000268637bd>] tls_init net/tls/tls_main.c:794 [inline]
[<00000000268637bd>] tls_init+0xbc/0x200 net/tls/tls_main.c:773
[<00000000f52c33c5>] __tcp_set_ulp net/ipv4/tcp_ulp.c:139 [inline]
[<00000000f52c33c5>] tcp_set_ulp+0xe2/0x190 net/ipv4/tcp_ulp.c:160
[<0000000009cb49a0>] do_tcp_setsockopt.isra.0+0x1c1/0xe10
net/ipv4/tcp.c:2825
[<00000000b9d96429>] tcp_setsockopt+0x71/0x80 net/ipv4/tcp.c:3152
[<0000000038a5546c>] sock_common_setsockopt+0x38/0x50
net/core/sock.c:3142
[<00000000d945b2a0>] __sys_setsockopt+0x10f/0x220 net/socket.c:2084
[<000000003c3afaa0>] __do_sys_setsockopt net/socket.c:2100 [inline]
[<000000003c3afaa0>] __se_sys_setsockopt net/socket.c:2097 [inline]
[<000000003c3afaa0>] __x64_sys_setsockopt+0x26/0x30 net/socket.c:2097
[<00000000f7f21cbd>] do_syscall_64+0x73/0x1f0
arch/x86/entry/common.c:290
[<00000000d4c003b9>] entry_SYSCALL_64_after_hwframe+0x44/0xa9
BUG: memory leak
unreferenced object 0xffff88810e3df600 (size 512):
comm "syz-executor.4", pid 6933, jiffies 4295090088 (age 13.620s)
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:
[<00000000e93f019a>] kmemleak_alloc_recursive
include/linux/kmemleak.h:43 [inline]
[<00000000e93f019a>] slab_post_alloc_hook mm/slab.h:586 [inline]
[<00000000e93f019a>] slab_alloc mm/slab.c:3319 [inline]
[<00000000e93f019a>] kmem_cache_alloc_trace+0x145/0x2c0 mm/slab.c:3548
[<00000000268637bd>] kmalloc include/linux/slab.h:552 [inline]
[<00000000268637bd>] kzalloc include/linux/slab.h:686 [inline]
[<00000000268637bd>] create_ctx net/tls/tls_main.c:611 [inline]
[<00000000268637bd>] tls_init net/tls/tls_main.c:794 [inline]
[<00000000268637bd>] tls_init+0xbc/0x200 net/tls/tls_main.c:773
[<00000000f52c33c5>] __tcp_set_ulp net/ipv4/tcp_ulp.c:139 [inline]
[<00000000f52c33c5>] tcp_set_ulp+0xe2/0x190 net/ipv4/tcp_ulp.c:160
[<0000000009cb49a0>] do_tcp_setsockopt.isra.0+0x1c1/0xe10
net/ipv4/tcp.c:2825
[<00000000b9d96429>] tcp_setsockopt+0x71/0x80 net/ipv4/tcp.c:3152
[<0000000038a5546c>] sock_common_setsockopt+0x38/0x50
net/core/sock.c:3142
[<00000000d945b2a0>] __sys_setsockopt+0x10f/0x220 net/socket.c:2084
[<000000003c3afaa0>] __do_sys_setsockopt net/socket.c:2100 [inline]
[<000000003c3afaa0>] __se_sys_setsockopt net/socket.c:2097 [inline]
[<000000003c3afaa0>] __x64_sys_setsockopt+0x26/0x30 net/socket.c:2097
[<00000000f7f21cbd>] do_syscall_64+0x73/0x1f0
arch/x86/entry/common.c:290
[<00000000d4c003b9>] 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-09-27 1:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-27 1:19 syzbot [this message]
2020-12-29 19:01 ` memory leak in tls_init Jakub Kicinski
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=00000000000047a6eb05937eaced@google.com \
--to=syzbot+35bc8fe94c9f38db8320@syzkaller.appspotmail.com \
--cc=aviadye@mellanox.com \
--cc=borisp@mellanox.com \
--cc=daniel@iogearbox.net \
--cc=davejwatson@fb.com \
--cc=davem@davemloft.net \
--cc=jakub.kicinski@netronome.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.