netlink: 24 bytes leftover after parsing attributes in process `syz-executor.5'. ====================================================== WARNING: possible circular locking dependency detected 4.14.218-syzkaller #0 Not tainted ------------------------------------------------------ device veth11 entered promiscuous mode kworker/u4:3/205 is trying to acquire lock: (k-sk_lock-AF_INET){+.+.}, at: [] lock_sock syzkaller/managers/linux-4-14/kernel/./include/net/sock.h:1471 [inline] (k-sk_lock-AF_INET){+.+.}, at: [] do_tcp_setsockopt.constprop.0+0xfb/0x1c10 syzkaller/managers/linux-4-14/kernel/net/ipv4/tcp.c:2562 but task is already holding lock: IPv6: ADDRCONF(NETDEV_UP): veth11: link is not ready ((&(&cp->cp_send_w)->work)){+.+.}, at: [] process_one_work+0x6e6/0x14a0 syzkaller/managers/linux-4-14/kernel/kernel/workqueue.c:2091 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 ((&(&cp->cp_send_w)->work)){+.+.}: flush_work+0xad/0x770 syzkaller/managers/linux-4-14/kernel/kernel/workqueue.c:2889 __cancel_work_timer+0x321/0x460 syzkaller/managers/linux-4-14/kernel/kernel/workqueue.c:2964 rds_tcp_reset_callbacks+0x18d/0x450 syzkaller/managers/linux-4-14/kernel/net/rds/tcp.c:167 rds_tcp_accept_one+0x61a/0x8b0 syzkaller/managers/linux-4-14/kernel/net/rds/tcp_listen.c:194 overlayfs: unrecognized mount option "./file0" or missing value rds_tcp_accept_worker+0x4d/0x70 syzkaller/managers/linux-4-14/kernel/net/rds/tcp.c:407 process_one_work+0x793/0x14a0 syzkaller/managers/linux-4-14/kernel/kernel/workqueue.c:2116 ucma_write: process 4149 (syz-executor.1) changed security contexts after opening file descriptor, this is not allowed. worker_thread+0x5cc/0xff0 syzkaller/managers/linux-4-14/kernel/kernel/workqueue.c:2250 kthread+0x30d/0x420 syzkaller/managers/linux-4-14/kernel/kernel/kthread.c:232 ret_from_fork+0x24/0x30 syzkaller/managers/linux-4-14/kernel/arch/x86/entry/entry_64.S:404 -> #0 (k-sk_lock-AF_INET){+.+.}: lock_acquire+0x170/0x3f0 syzkaller/managers/linux-4-14/kernel/kernel/locking/lockdep.c:3998 lock_sock_nested+0xb7/0x100 syzkaller/managers/linux-4-14/kernel/net/core/sock.c:2796 lock_sock syzkaller/managers/linux-4-14/kernel/./include/net/sock.h:1471 [inline] do_tcp_setsockopt.constprop.0+0xfb/0x1c10 syzkaller/managers/linux-4-14/kernel/net/ipv4/tcp.c:2562 tcp_setsockopt syzkaller/managers/linux-4-14/kernel/net/ipv4/tcp.c:2830 [inline] tcp_setsockopt+0xa7/0xc0 syzkaller/managers/linux-4-14/kernel/net/ipv4/tcp.c:2822 kernel_setsockopt+0xfb/0x1b0 syzkaller/managers/linux-4-14/kernel/net/socket.c:3396 rds_tcp_cork syzkaller/managers/linux-4-14/kernel/net/rds/tcp_send.c:43 [inline] rds_tcp_xmit_path_prepare+0xaf/0xe0 syzkaller/managers/linux-4-14/kernel/net/rds/tcp_send.c:50 rds_send_xmit+0x1ae/0x1c00 syzkaller/managers/linux-4-14/kernel/net/rds/send.c:187 rds_send_worker+0x6d/0x240 syzkaller/managers/linux-4-14/kernel/net/rds/threads.c:189 process_one_work+0x793/0x14a0 syzkaller/managers/linux-4-14/kernel/kernel/workqueue.c:2116 worker_thread+0x5cc/0xff0 syzkaller/managers/linux-4-14/kernel/kernel/workqueue.c:2250 kthread+0x30d/0x420 syzkaller/managers/linux-4-14/kernel/kernel/kthread.c:232 ret_from_fork+0x24/0x30 syzkaller/managers/linux-4-14/kernel/arch/x86/entry/entry_64.S:404 other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock((&(&cp->cp_send_w)->work)); lock(k-sk_lock-AF_INET); lock((&(&cp->cp_send_w)->work)); lock(k-sk_lock-AF_INET); *** DEADLOCK *** 2 locks held by kworker/u4:3/205: #0: ("%s""krdsd"){+.+.}, at: [] process_one_work+0x6b0/0x14a0 syzkaller/managers/linux-4-14/kernel/kernel/workqueue.c:2087 #1: ((&(&cp->cp_send_w)->work)){+.+.}, at: [] process_one_work+0x6e6/0x14a0 syzkaller/managers/linux-4-14/kernel/kernel/workqueue.c:2091 stack backtrace: CPU: 0 PID: 205 Comm: kworker/u4:3 Not tainted 4.14.218-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Workqueue: krdsd rds_send_worker Call Trace: __dump_stack syzkaller/managers/linux-4-14/kernel/lib/dump_stack.c:17 [inline] dump_stack+0x1b2/0x281 syzkaller/managers/linux-4-14/kernel/lib/dump_stack.c:58 print_circular_bug.constprop.0.cold+0x2d7/0x41e syzkaller/managers/linux-4-14/kernel/kernel/locking/lockdep.c:1258 check_prev_add syzkaller/managers/linux-4-14/kernel/kernel/locking/lockdep.c:1905 [inline] check_prevs_add syzkaller/managers/linux-4-14/kernel/kernel/locking/lockdep.c:2022 [inline] validate_chain syzkaller/managers/linux-4-14/kernel/kernel/locking/lockdep.c:2464 [inline] __lock_acquire+0x2e0e/0x3f20 syzkaller/managers/linux-4-14/kernel/kernel/locking/lockdep.c:3491 lock_acquire+0x170/0x3f0 syzkaller/managers/linux-4-14/kernel/kernel/locking/lockdep.c:3998 lock_sock_nested+0xb7/0x100 syzkaller/managers/linux-4-14/kernel/net/core/sock.c:2796 lock_sock syzkaller/managers/linux-4-14/kernel/./include/net/sock.h:1471 [inline] do_tcp_setsockopt.constprop.0+0xfb/0x1c10 syzkaller/managers/linux-4-14/kernel/net/ipv4/tcp.c:2562 tcp_setsockopt syzkaller/managers/linux-4-14/kernel/net/ipv4/tcp.c:2830 [inline] tcp_setsockopt+0xa7/0xc0 syzkaller/managers/linux-4-14/kernel/net/ipv4/tcp.c:2822 kernel_setsockopt+0xfb/0x1b0 syzkaller/managers/linux-4-14/kernel/net/socket.c:3396 rds_tcp_cork syzkaller/managers/linux-4-14/kernel/net/rds/tcp_send.c:43 [inline] rds_tcp_xmit_path_prepare+0xaf/0xe0 syzkaller/managers/linux-4-14/kernel/net/rds/tcp_send.c:50 rds_send_xmit+0x1ae/0x1c00 syzkaller/managers/linux-4-14/kernel/net/rds/send.c:187 rds_send_worker+0x6d/0x240 syzkaller/managers/linux-4-14/kernel/net/rds/threads.c:189 process_one_work+0x793/0x14a0 syzkaller/managers/linux-4-14/kernel/kernel/workqueue.c:2116 worker_thread+0x5cc/0xff0 syzkaller/managers/linux-4-14/kernel/kernel/workqueue.c:2250 kthread+0x30d/0x420 syzkaller/managers/linux-4-14/kernel/kernel/kthread.c:232 ret_from_fork+0x24/0x30 syzkaller/managers/linux-4-14/kernel/arch/x86/entry/entry_64.S:404 overlayfs: unrecognized mount option "./file0" or missing value netlink: 24 bytes leftover after parsing attributes in process `syz-executor.4'. overlayfs: unrecognized mount option "./file0" or missing value device veth15 entered promiscuous mode IPv6: ADDRCONF(NETDEV_UP): veth15: link is not ready FAULT_INJECTION: forcing a failure. name failslab, interval 1, probability 0, space 0, times 0 FAULT_INJECTION: forcing a failure. name failslab, interval 1, probability 0, space 0, times 0 CPU: 0 PID: 19873 Comm: syz-executor.5 Not tainted 4.14.218-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: __dump_stack syzkaller/managers/linux-4-14/kernel/lib/dump_stack.c:17 [inline] dump_stack+0x1b2/0x281 syzkaller/managers/linux-4-14/kernel/lib/dump_stack.c:58 fail_dump syzkaller/managers/linux-4-14/kernel/lib/fault-inject.c:51 [inline] should_fail.cold+0x10a/0x149 syzkaller/managers/linux-4-14/kernel/lib/fault-inject.c:149 should_failslab+0xd6/0x130 syzkaller/managers/linux-4-14/kernel/mm/failslab.c:32 slab_pre_alloc_hook syzkaller/managers/linux-4-14/kernel/mm/slab.h:421 [inline] slab_alloc syzkaller/managers/linux-4-14/kernel/mm/slab.c:3376 [inline] __do_kmalloc syzkaller/managers/linux-4-14/kernel/mm/slab.c:3718 [inline] __kmalloc_track_caller+0x2bc/0x400 syzkaller/managers/linux-4-14/kernel/mm/slab.c:3735 memdup_user+0x22/0xa0 syzkaller/managers/linux-4-14/kernel/mm/util.c:164 strndup_user+0x5b/0xf0 syzkaller/managers/linux-4-14/kernel/mm/util.c:195 SYSC_request_key syzkaller/managers/linux-4-14/kernel/security/keys/keyctl.c:174 [inline] SyS_request_key+0xbe/0x2f0 syzkaller/managers/linux-4-14/kernel/security/keys/keyctl.c:156 do_syscall_64+0x1d5/0x640 syzkaller/managers/linux-4-14/kernel/arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x46/0xbb RIP: 0033:0x465b09 RSP: 002b:00007fbd35b0a188 EFLAGS: 00000246 ORIG_RAX: 00000000000000f9 RAX: ffffffffffffffda RBX: 000000000056bf60 RCX: 0000000000465b09 RDX: 0000000000000000 RSI: 0000000020000680 RDI: 0000000020000580 RBP: 00007fbd35b0a1d0 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001 R13: 00007ffe795230ff R14: 00007fbd35b0a300 R15: 0000000000022000 CPU: 1 PID: 19878 Comm: syz-executor.4 Not tainted 4.14.218-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: __dump_stack syzkaller/managers/linux-4-14/kernel/lib/dump_stack.c:17 [inline] dump_stack+0x1b2/0x281 syzkaller/managers/linux-4-14/kernel/lib/dump_stack.c:58 fail_dump syzkaller/managers/linux-4-14/kernel/lib/fault-inject.c:51 [inline] should_fail.cold+0x10a/0x149 syzkaller/managers/linux-4-14/kernel/lib/fault-inject.c:149 should_failslab+0xd6/0x130 syzkaller/managers/linux-4-14/kernel/mm/failslab.c:32 slab_pre_alloc_hook syzkaller/managers/linux-4-14/kernel/mm/slab.h:421 [inline] slab_alloc syzkaller/managers/linux-4-14/kernel/mm/slab.c:3376 [inline] __do_kmalloc syzkaller/managers/linux-4-14/kernel/mm/slab.c:3718 [inline] __kmalloc+0x2c1/0x400 syzkaller/managers/linux-4-14/kernel/mm/slab.c:3729 kmalloc syzkaller/managers/linux-4-14/kernel/./include/linux/slab.h:493 [inline] do_tty_write syzkaller/managers/linux-4-14/kernel/drivers/tty/tty_io.c:941 [inline] tty_write+0x4e0/0x740 syzkaller/managers/linux-4-14/kernel/drivers/tty/tty_io.c:1043 __vfs_write+0xe4/0x630 syzkaller/managers/linux-4-14/kernel/fs/read_write.c:480 vfs_write+0x17f/0x4d0 syzkaller/managers/linux-4-14/kernel/fs/read_write.c:544 SYSC_write syzkaller/managers/linux-4-14/kernel/fs/read_write.c:590 [inline] SyS_write+0xf2/0x210 syzkaller/managers/linux-4-14/kernel/fs/read_write.c:582 do_syscall_64+0x1d5/0x640 syzkaller/managers/linux-4-14/kernel/arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x46/0xbb RIP: 0033:0x465b09 RSP: 002b:00007f9d74714188 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 RAX: ffffffffffffffda RBX: 000000000056bf60 RCX: 0000000000465b09 RDX: 000000000000021d RSI: 0000000020000140 RDI: 0000000000000004 RBP: 00007f9d747141d0 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001 R13: 00007ffd1d06e3bf R14: 00007f9d74714300 R15: 0000000000022000 netlink: 24 bytes leftover after parsing attributes in process `syz-executor.2'. device veth17 entered promiscuous mode IPv6: ADDRCONF(NETDEV_UP): veth17: link is not ready netlink: 24 bytes leftover after parsing attributes in process `syz-executor.2'. netlink: 84 bytes leftover after parsing attributes in process `syz-executor.0'. netlink: 84 bytes leftover after parsing attributes in process `syz-executor.0'. hfs: unable to parse mount options print_req_error: I/O error, dev loop4, sector 0 hfs: unable to parse mount options could not allocate digest TFM handle blake2s-224-generic could not allocate digest TFM handle blake2s-224-generic could not allocate digest TFM handle blake2s-224-generic netlink: 24 bytes leftover after parsing attributes in process `syz-executor.5'.