[<prev] [next>] [day] [month] [year] [list]
Message-ID: <00000000000023a7e70581b71894@google.com>
Date: Tue, 12 Feb 2019 11:04:27 -0800
From: syzbot <syzbot+3d07f0ffd652af4f49e6@...kaller.appspotmail.com>
To: gregkh@...uxfoundation.org, linux-kernel@...r.kernel.org,
syzkaller-bugs@...glegroups.com, tj@...nel.org
Subject: general protection fault in idr_remove
Hello,
syzbot found the following crash on:
HEAD commit: b5829453d81a Add linux-next specific files for 20190212
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1662de24c00000
kernel config: https://syzkaller.appspot.com/x/.config?x=4085ec231ef9027d
dashboard link: https://syzkaller.appspot.com/bug?extid=3d07f0ffd652af4f49e6
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+3d07f0ffd652af4f49e6@...kaller.appspotmail.com
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 16586 Comm: syz-executor.5 Not tainted 5.0.0-rc6-next-20190212
#33
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:idr_remove+0x28/0x60 lib/idr.c:153
Code: 40 00 55 48 89 e5 41 54 49 89 fc 53 48 89 f3 e8 9e a5 6f fa 49 8d 7c
24 48 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 <0f> b6 04 02 84
c0 74 04 3c 03 7e 1a 41 8b 44 24 48 4c 89 e7 31 d2
RSP: 0018:ffff8880263c7820 EFLAGS: 00010202
RAX: dffffc0000000000 RBX: 00000000000180a4 RCX: ffffc90010870000
RDX: 000000000000020b RSI: ffffffff8700a952 RDI: 0000000000001058
RBP: ffff8880263c7830 R08: 1ffff11004c78ef5 R09: ffffed1004c78ef6
R10: ffffed1004c78ef5 R11: 0000000000000003 R12: 0000000000001010
R13: ffff88808eb137e0 R14: 0000000000000001 R15: 0000000000000000
FS: 00007f1aa164c700(0000) GS:ffff8880ae800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fbbc506316b CR3: 00000000a9547000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600
Call Trace:
kernfs_put fs/kernfs/dir.c:542 [inline]
kernfs_put+0x342/0x600 fs/kernfs/dir.c:506
kernfs_create_dir_ns+0x135/0x160 fs/kernfs/dir.c:1035
sysfs_create_dir_ns+0x131/0x2a0 fs/sysfs/dir.c:59
create_dir lib/kobject.c:88 [inline]
kobject_add_internal lib/kobject.c:247 [inline]
kobject_add_internal.cold+0xe5/0x5d4 lib/kobject.c:217
kobject_add_varg lib/kobject.c:382 [inline]
kobject_add+0x150/0x1c0 lib/kobject.c:426
device_add+0x3d5/0x18a0 drivers/base/core.c:2070
hci_register_dev+0x304/0x880 net/bluetooth/hci_core.c:3264
__vhci_create_device+0x2d0/0x5a0 drivers/bluetooth/hci_vhci.c:139
vhci_create_device drivers/bluetooth/hci_vhci.c:163 [inline]
vhci_get_user drivers/bluetooth/hci_vhci.c:219 [inline]
vhci_write+0x2d0/0x470 drivers/bluetooth/hci_vhci.c:299
call_write_iter include/linux/fs.h:1853 [inline]
new_sync_write fs/read_write.c:474 [inline]
__vfs_write+0x613/0x8e0 fs/read_write.c:487
vfs_write+0x20c/0x580 fs/read_write.c:549
ksys_write+0xea/0x1f0 fs/read_write.c:598
__do_sys_write fs/read_write.c:610 [inline]
__se_sys_write fs/read_write.c:607 [inline]
__x64_sys_write+0x73/0xb0 fs/read_write.c:607
do_syscall_64+0x103/0x610 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x457e39
Code: ad b8 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 89 f8 48 89 f7
48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff
ff 0f 83 7b b8 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f1aa164bc78 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 0000000000457e39
RDX: 0000000000000002 RSI: 00000000200000c0 RDI: 0000000000000005
RBP: 000000000073bf00 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f1aa164c6d4
R13: 00000000004c6e80 R14: 00000000004dc6a0 R15: 00000000ffffffff
Modules linked in:
---[ end trace 7fdd458eb72d2ee0 ]---
RIP: 0010:idr_remove+0x28/0x60 lib/idr.c:153
Code: 40 00 55 48 89 e5 41 54 49 89 fc 53 48 89 f3 e8 9e a5 6f fa 49 8d 7c
24 48 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 <0f> b6 04 02 84
c0 74 04 3c 03 7e 1a 41 8b 44 24 48 4c 89 e7 31 d2
RSP: 0018:ffff8880263c7820 EFLAGS: 00010202
RAX: dffffc0000000000 RBX: 00000000000180a4 RCX: ffffc90010870000
RDX: 000000000000020b RSI: ffffffff8700a952 RDI: 0000000000001058
RBP: ffff8880263c7830 R08: 1ffff11004c78ef5 R09: ffffed1004c78ef6
R10: ffffed1004c78ef5 R11: 0000000000000003 R12: 0000000000001010
R13: ffff88808eb137e0 R14: 0000000000000001 R15: 0000000000000000
FS: 00007f1aa164c700(0000) GS:ffff8880ae800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fbbc506316b CR3: 00000000a9547000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600
---
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@...glegroups.com.
syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#bug-status-tracking for how to communicate with
syzbot.
Powered by blists - more mailing lists