From: syzbot <syzbot+6ce141c55b2f7aafd1c4@syzkaller.appspotmail.com>
To: johan.hedberg@gmail.com, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org, marcel@holtmann.org,
syzkaller-bugs@googlegroups.com
Subject: memory leak in h5_rx_pkt_start
Date: Mon, 16 Sep 2019 09:09:07 -0700 [thread overview]
Message-ID: <000000000000d0cc780592add25d@google.com> (raw)
Hello,
syzbot found the following crash on:
HEAD commit: 1609d760 Merge tag 'for-linus' of git://git.kernel.org/pub..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1494a081600000
kernel config: https://syzkaller.appspot.com/x/.config?x=90cbcb59581ed842
dashboard link: https://syzkaller.appspot.com/bug?extid=6ce141c55b2f7aafd1c4
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12185479600000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1238c465600000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+6ce141c55b2f7aafd1c4@syzkaller.appspotmail.com
executing program
executing program
executing program
executing program
executing program
BUG: memory leak
unreferenced object 0xffff88811469e100 (size 224):
comm "syz-executor068", pid 6860, jiffies 4294949784 (age 13.480s)
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 c0 bf 20 81 88 ff ff 00 00 00 00 00 00 00 00 ... ............
backtrace:
[<0000000036b71133>] kmemleak_alloc_recursive
include/linux/kmemleak.h:43 [inline]
[<0000000036b71133>] slab_post_alloc_hook mm/slab.h:522 [inline]
[<0000000036b71133>] slab_alloc_node mm/slab.c:3262 [inline]
[<0000000036b71133>] kmem_cache_alloc_node+0x163/0x2f0 mm/slab.c:3574
[<00000000c50cdaae>] __alloc_skb+0x6e/0x210 net/core/skbuff.c:197
[<0000000097f6a43a>] alloc_skb include/linux/skbuff.h:1055 [inline]
[<0000000097f6a43a>] bt_skb_alloc include/net/bluetooth/bluetooth.h:339
[inline]
[<0000000097f6a43a>] h5_rx_pkt_start+0x57/0xd0
drivers/bluetooth/hci_h5.c:474
[<00000000d2c8fdbf>] h5_recv+0x13f/0x1d0 drivers/bluetooth/hci_h5.c:563
[<00000000c4a86230>] hci_uart_tty_receive+0xba/0x200
drivers/bluetooth/hci_ldisc.c:613
[<0000000039786cc4>] tiocsti drivers/tty/tty_io.c:2197 [inline]
[<0000000039786cc4>] tty_ioctl+0x81c/0xa30 drivers/tty/tty_io.c:2573
[<00000000ba214ddb>] vfs_ioctl fs/ioctl.c:46 [inline]
[<00000000ba214ddb>] file_ioctl fs/ioctl.c:509 [inline]
[<00000000ba214ddb>] do_vfs_ioctl+0x62a/0x810 fs/ioctl.c:696
[<00000000fa2c3356>] ksys_ioctl+0x86/0xb0 fs/ioctl.c:713
[<00000000eab0a027>] __do_sys_ioctl fs/ioctl.c:720 [inline]
[<00000000eab0a027>] __se_sys_ioctl fs/ioctl.c:718 [inline]
[<00000000eab0a027>] __x64_sys_ioctl+0x1e/0x30 fs/ioctl.c:718
[<00000000db7e89eb>] do_syscall_64+0x76/0x1a0
arch/x86/entry/common.c:296
[<000000008887ecc0>] 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
reply other threads:[~2019-09-16 16:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=000000000000d0cc780592add25d@google.com \
--to=syzbot+6ce141c55b2f7aafd1c4@syzkaller.appspotmail.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.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.