====================================================== WARNING: possible circular locking dependency detected 4.20.0-rc6-next-20181217+ #172 Not tainted ------------------------------------------------------ syz-executor0/7514 is trying to acquire lock: 000000004c35cae0 (&tbl->lock){+.-.}, at: neigh_change_state+0x1dc/0x7a0 net/core/neighbour.c:141 but task is already holding lock: 000000006d1062ba (&n->lock){++--}, at: __neigh_update+0xe6/0x1eb0 net/core/neighbour.c:1203 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&n->lock){++--}: __raw_write_lock include/linux/rwlock_api_smp.h:210 [inline] _raw_write_lock+0x2d/0x40 kernel/locking/spinlock.c:288 neigh_periodic_work+0x3c0/0xc30 net/core/neighbour.c:894 process_one_work+0xc90/0x1c40 kernel/workqueue.c:2153 worker_thread+0x17f/0x1390 kernel/workqueue.c:2296 kthread+0x35a/0x440 kernel/kthread.c:246 ret_from_fork+0x3a/0x50 arch/x86/entry/entry_64.S:352 -> #0 (&tbl->lock){+.-.}: lock_acquire+0x1ed/0x520 kernel/locking/lockdep.c:3841 __raw_write_lock_bh include/linux/rwlock_api_smp.h:203 [inline] _raw_write_lock_bh+0x31/0x40 kernel/locking/spinlock.c:312 neigh_change_state+0x1dc/0x7a0 net/core/neighbour.c:141 __neigh_update+0x478/0x1eb0 net/core/neighbour.c:1302 neigh_update+0x37/0x50 net/core/neighbour.c:1372 arp_req_set+0x54c/0xaa0 net/ipv4/arp.c:1072 arp_ioctl+0x48b/0xae0 net/ipv4/arp.c:1230 inet_ioctl+0x237/0x360 net/ipv4/af_inet.c:932 sock_do_ioctl+0xeb/0x420 net/socket.c:951 sock_ioctl+0x313/0x690 net/socket.c:1075 vfs_ioctl fs/ioctl.c:46 [inline] file_ioctl fs/ioctl.c:509 [inline] do_vfs_ioctl+0x1de/0x1790 fs/ioctl.c:696 ksys_ioctl+0xa9/0xd0 fs/ioctl.c:713 __do_sys_ioctl fs/ioctl.c:720 [inline] __se_sys_ioctl fs/ioctl.c:718 [inline] __x64_sys_ioctl+0x73/0xb0 fs/ioctl.c:718 do_syscall_64+0x1b9/0x820 arch/x86/entry/common.c:290 entry_SYSCALL_64_after_hwframe+0x49/0xbe other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&n->lock); lock(&tbl->lock); lock(&n->lock); lock(&tbl->lock); *** DEADLOCK *** 2 locks held by syz-executor0/7514: #0: 00000000600cbef1 (rtnl_mutex){+.+.}, at: rtnl_lock+0x17/0x20 net/core/rtnetlink.c:77 #1: 000000006d1062ba (&n->lock){++--}, at: __neigh_update+0xe6/0x1eb0 net/core/neighbour.c:1203 stack backtrace: CPU: 0 PID: 7514 Comm: syz-executor0 Not tainted 4.20.0-rc6-next-20181217+ #172 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x244/0x39d lib/dump_stack.c:113 print_circular_bug.isra.36.cold.58+0x1bd/0x27d kernel/locking/lockdep.c:1224 check_prev_add kernel/locking/lockdep.c:1866 [inline] check_prevs_add kernel/locking/lockdep.c:1979 [inline] validate_chain kernel/locking/lockdep.c:2350 [inline] __lock_acquire+0x3399/0x4c20 kernel/locking/lockdep.c:3338 lock_acquire+0x1ed/0x520 kernel/locking/lockdep.c:3841 __raw_write_lock_bh include/linux/rwlock_api_smp.h:203 [inline] _raw_write_lock_bh+0x31/0x40 kernel/locking/spinlock.c:312 neigh_change_state+0x1dc/0x7a0 net/core/neighbour.c:141 __neigh_update+0x478/0x1eb0 net/core/neighbour.c:1302 neigh_update+0x37/0x50 net/core/neighbour.c:1372 arp_req_set+0x54c/0xaa0 net/ipv4/arp.c:1072 arp_ioctl+0x48b/0xae0 net/ipv4/arp.c:1230 inet_ioctl+0x237/0x360 net/ipv4/af_inet.c:932 sock_do_ioctl+0xeb/0x420 net/socket.c:951 sock_ioctl+0x313/0x690 net/socket.c:1075 vfs_ioctl fs/ioctl.c:46 [inline] file_ioctl fs/ioctl.c:509 [inline] do_vfs_ioctl+0x1de/0x1790 fs/ioctl.c:696 ksys_ioctl+0xa9/0xd0 fs/ioctl.c:713 __do_sys_ioctl fs/ioctl.c:720 [inline] __se_sys_ioctl fs/ioctl.c:718 [inline] __x64_sys_ioctl+0x73/0xb0 fs/ioctl.c:718 do_syscall_64+0x1b9/0x820 arch/x86/entry/common.c:290 entry_SYSCALL_64_after_hwframe+0x49/0xbe RIP: 0033:0x457669 Code: fd b3 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 cb b3 fb ff c3 66 2e 0f 1f 84 00 00 00 00 RSP: 002b:00007fa0bf578c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 0000000000457669 RDX: 0000000020000040 RSI: 0000000000008955 RDI: 0000000000000007 RBP: 000000000072bfa0 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 00007fa0bf5796d4 R13: 00000000004c0acd R14: 00000000004d1c98 R15: 00000000ffffffff kobject: 'loop0' (000000006ff4df94): kobject_uevent_env kobject: 'loop0' (000000006ff4df94): fill_kobj_path: path = '/devices/virtual/block/loop0' kobject: 'loop0' (000000006ff4df94): kobject_uevent_env kobject: 'loop0' (000000006ff4df94): fill_kobj_path: path = '/devices/virtual/block/loop0' kobject: 'loop0' (000000006ff4df94): kobject_uevent_env kobject: 'loop0' (000000006ff4df94): fill_kobj_path: path = '/devices/virtual/block/loop0' kobject: 'loop0' (000000006ff4df94): kobject_uevent_env kobject: 'loop0' (000000006ff4df94): fill_kobj_path: path = '/devices/virtual/block/loop0' kobject: 'loop1' (00000000c90c174a): kobject_uevent_env kobject: 'loop1' (00000000c90c174a): fill_kobj_path: path = '/devices/virtual/block/loop1' L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/l1tf.html for details. kobject: 'kvm' (000000008e5f0d3a): kobject_uevent_env kobject: 'kvm' (000000008e5f0d3a): fill_kobj_path: path = '/devices/virtual/misc/kvm' kobject: 'kvm' (000000008e5f0d3a): kobject_uevent_env ================================================================== BUG: KASAN: slab-out-of-bounds in memset include/linux/string.h:337 [inline] BUG: KASAN: slab-out-of-bounds in fpstate_init+0x50/0x160 arch/x86/kernel/fpu/core.c:178 Write of size 832 at addr ffff8881cce89bc0 by task syz-executor1/7632 CPU: 1 PID: 7632 Comm: syz-executor1 Not tainted 4.20.0-rc6-next-20181217+ #172 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x244/0x39d lib/dump_stack.c:113 kobject: 'loop2' (00000000a25dea3a): kobject_uevent_env print_address_description.cold.4+0x9/0x1ff mm/kasan/report.c:187 kobject: 'kvm' (000000008e5f0d3a): fill_kobj_path: path = '/devices/virtual/misc/kvm' kasan_report.cold.5+0x1b/0x39 mm/kasan/report.c:317 kobject: 'loop2' (00000000a25dea3a): fill_kobj_path: path = '/devices/virtual/block/loop2' check_memory_region_inline mm/kasan/generic.c:185 [inline] check_memory_region+0x13e/0x1b0 mm/kasan/generic.c:191 memset+0x23/0x40 mm/kasan/common.c:113 memset include/linux/string.h:337 [inline] fpstate_init+0x50/0x160 arch/x86/kernel/fpu/core.c:178 fx_init arch/x86/kvm/x86.c:8646 [inline] kvm_arch_vcpu_init+0x3e9/0x870 arch/x86/kvm/x86.c:9006 kvm_vcpu_init+0x2fa/0x420 arch/x86/kvm/../../../virt/kvm/kvm_main.c:315 vmx_create_vcpu+0x1b7/0x2695 arch/x86/kvm/vmx/vmx.c:6375 kvm_arch_vcpu_create+0xe5/0x220 arch/x86/kvm/x86.c:8679 kvm_vm_ioctl_create_vcpu arch/x86/kvm/../../../virt/kvm/kvm_main.c:2555 [inline] kvm_vm_ioctl+0x526/0x2030 arch/x86/kvm/../../../virt/kvm/kvm_main.c:3084 vfs_ioctl fs/ioctl.c:46 [inline] file_ioctl fs/ioctl.c:509 [inline] do_vfs_ioctl+0x1de/0x1790 fs/ioctl.c:696 ksys_ioctl+0xa9/0xd0 fs/ioctl.c:713 __do_sys_ioctl fs/ioctl.c:720 [inline] __se_sys_ioctl fs/ioctl.c:718 [inline] __x64_sys_ioctl+0x73/0xb0 fs/ioctl.c:718 do_syscall_64+0x1b9/0x820 arch/x86/entry/common.c:290 entry_SYSCALL_64_after_hwframe+0x49/0xbe RIP: 0033:0x457669 Code: fd b3 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 cb b3 fb ff c3 66 2e 0f 1f 84 00 00 00 00 RSP: 002b:00007f7a1c1ddc78 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 0000000000457669 RDX: 0000000000000000 RSI: 000000000000ae41 RDI: 0000000000000004 RBP: 000000000072bfa0 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 00007f7a1c1de6d4 R13: 00000000004c00ff R14: 00000000004d1170 R15: 00000000ffffffff Allocated by task 7632: save_stack+0x43/0xd0 mm/kasan/common.c:73 set_track mm/kasan/common.c:85 [inline] kasan_kmalloc+0xcb/0xd0 mm/kasan/common.c:482 kasan_slab_alloc+0x12/0x20 mm/kasan/common.c:397 kmem_cache_alloc+0x130/0x730 mm/slab.c:3541 kmem_cache_zalloc include/linux/slab.h:730 [inline] vmx_create_vcpu+0x110/0x2695 arch/x86/kvm/vmx/vmx.c:6366 kvm_arch_vcpu_create+0xe5/0x220 arch/x86/kvm/x86.c:8679 kvm_vm_ioctl_create_vcpu arch/x86/kvm/../../../virt/kvm/kvm_main.c:2555 [inline] kvm_vm_ioctl+0x526/0x2030 arch/x86/kvm/../../../virt/kvm/kvm_main.c:3084 vfs_ioctl fs/ioctl.c:46 [inline] file_ioctl fs/ioctl.c:509 [inline] do_vfs_ioctl+0x1de/0x1790 fs/ioctl.c:696 ksys_ioctl+0xa9/0xd0 fs/ioctl.c:713 __do_sys_ioctl fs/ioctl.c:720 [inline] __se_sys_ioctl fs/ioctl.c:718 [inline] __x64_sys_ioctl+0x73/0xb0 fs/ioctl.c:718 do_syscall_64+0x1b9/0x820 arch/x86/entry/common.c:290 entry_SYSCALL_64_after_hwframe+0x49/0xbe Freed by task 0: (stack is not available) The buggy address belongs to the object at ffff8881cce89b80 which belongs to the cache x86_fpu of size 832 The buggy address is located 64 bytes inside of 832-byte region [ffff8881cce89b80, ffff8881cce89ec0) The buggy address belongs to the page: page:ffffea000733a240 count:1 mapcount:0 mapping:ffff8881d792e500 index:0x0 flags: 0x2fffc0000000200(slab) raw: 02fffc0000000200 ffff8881d5091f48 ffff8881d5091f48 ffff8881d792e500 raw: 0000000000000000 ffff8881cce89040 0000000100000004 0000000000000000 page dumped because: kasan: bad access detected Memory state around the buggy address: ffff8881cce89d80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffff8881cce89e00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >ffff8881cce89e80: 00 00 00 00 00 00 00 00 fc fc fc fc fc fc fc fc ^ ffff8881cce89f00: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc ffff8881cce89f80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc ==================================================================