Hello,
syzbot found the following crash on:
HEAD commit: 01364dad Linux 4.14.174
git tree: linux-4.14.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=1728dce5e00000
kernel config:
https://syzkaller.appspot.com/x/.config?x=664dd71881ab2b2d
dashboard link:
https://syzkaller.appspot.com/bug?extid=ed209d00d1a00ff450e8
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
Unfortunately, I don't have any reproducer for this crash yet.
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by:
syzbot+ed209d...@syzkaller.appspotmail.com
audit: type=1400 audit(2000000022.890:63): avc: denied { map } for pid=9234 comm="syz-executor.5" path="/dev/ashmem" dev="devtmpfs" ino=17521 scontext=unconfined_u:system_r:insmod_t:s0-s0:c0.c1023 tcontext=system_u:object_r:device_t:s0 tclass=chr_file permissive=1
ip6_tables: ip6tables: counters copy to user failed while replacing table
ODEBUG: free active (active state 0) object type: timer_list hint: __write_once_size include/linux/compiler.h:210 [inline]
ODEBUG: free active (active state 0) object type: timer_list hint: __list_add include/linux/list.h:66 [inline]
ODEBUG: free active (active state 0) object type: timer_list hint: list_add include/linux/list.h:79 [inline]
ODEBUG: free active (active state 0) object type: timer_list hint: rfcomm_dlc_timeout+0x0/0x60 net/bluetooth/rfcomm/core.c:337
------------[ cut here ]------------
WARNING: CPU: 0 PID: 9250 at lib/debugobjects.c:287 debug_print_object.cold+0xa7/0xdb lib/debugobjects.c:287
Kernel panic - not syncing: panic_on_warn set ...
CPU: 0 PID: 9250 Comm: syz-executor.0 Not tainted 4.14.174-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x13e/0x194 lib/dump_stack.c:58
panic+0x1f9/0x42d kernel/panic.c:183
__warn.cold+0x2f/0x30 kernel/panic.c:547
report_bug+0x20a/0x248 lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:177 [inline]
fixup_bug arch/x86/kernel/traps.c:172 [inline]
do_error_trap+0x195/0x2d0 arch/x86/kernel/traps.c:295
invalid_op+0x1b/0x40 arch/x86/entry/entry_64.S:963
RIP: 0010:debug_print_object.cold+0xa7/0xdb lib/debugobjects.c:287
RSP: 0018:ffff88804b50fb10 EFLAGS: 00010086
RAX: 000000000000005e RBX: 0000000000000003 RCX: 0000000000000000
RDX: 0000000000028629 RSI: ffffffff81491370 RDI: ffffed10096a1f58
RBP: ffffffff86abba60 R08: 000000000000005e R09: 0000000000000000
R10: fffffbfff14a8cd9 R11: ffff8880991a8600 R12: ffffffff85a89100
R13: 0000000000000000 R14: ffffffff8a760c88 R15: ffff888096350850
__debug_check_no_obj_freed lib/debugobjects.c:747 [inline]
debug_check_no_obj_freed+0x3cd/0x6e4 lib/debugobjects.c:776
kfree+0xbb/0x260 mm/slab.c:3814
rfcomm_dlc_put include/net/bluetooth/rfcomm.h:258 [inline]
__rfcomm_create_dev net/bluetooth/rfcomm/tty.c:417 [inline]
rfcomm_create_dev net/bluetooth/rfcomm/tty.c:486 [inline]
rfcomm_dev_ioctl+0x151f/0x1810 net/bluetooth/rfcomm/tty.c:588
rfcomm_sock_ioctl+0x7d/0xa0 net/bluetooth/rfcomm/sock.c:902
sock_do_ioctl+0x5f/0xa0 net/socket.c:974
sock_ioctl+0x28d/0x450 net/socket.c:1071
vfs_ioctl fs/ioctl.c:46 [inline]
file_ioctl fs/ioctl.c:500 [inline]
do_vfs_ioctl+0x75a/0xfe0 fs/ioctl.c:684
SYSC_ioctl fs/ioctl.c:701 [inline]
SyS_ioctl+0x7f/0xb0 fs/ioctl.c:692
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x45c849
RSP: 002b:00007f79586a9c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f79586aa6d4 RCX: 000000000045c849
RDX: 0000000020000100 RSI: 00000000400452c8 RDI: 0000000000000004
RBP: 000000000076bf00 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000ffffffff
R13: 0000000000000316 R14: 00000000004c57dd R15: 000000000076bf0c
======================================================
---
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
syzk...@googlegroups.com.
syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.