overlayfs: filesystem on './bus' not supported as upperdir ====================================================== WARNING: possible circular locking dependency detected 4.19.195-syzkaller #0 Not tainted ------------------------------------------------------ kworker/u4:4/216 is trying to acquire lock: 00000000edac816b ((wq_completion)"events"){+.+.}, at: flush_workqueue+0xe8/0x13e0 kernel/workqueue.c:2658 but task is already holding lock: 00000000da9fa966 (pernet_ops_rwsem){++++}, at: cleanup_net+0xa8/0x8b0 net/core/net_namespace.c:520 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #3 (pernet_ops_rwsem){++++}: unregister_netdevice_notifier+0x7b/0x330 net/core/dev.c:1708 bcm_release+0x94/0x700 net/can/bcm.c:1525 __sock_release+0xcd/0x2a0 net/socket.c:579 sock_close+0x15/0x20 net/socket.c:1140 __fput+0x2ce/0x890 fs/file_table.c:278 task_work_run+0x148/0x1c0 kernel/task_work.c:113 get_signal+0x1b64/0x1f70 kernel/signal.c:2400 do_signal+0x8f/0x1670 arch/x86/kernel/signal.c:799 exit_to_usermode_loop+0x204/0x2a0 arch/x86/entry/common.c:163 prepare_exit_to_usermode arch/x86/entry/common.c:198 [inline] syscall_return_slowpath arch/x86/entry/common.c:271 [inline] do_syscall_64+0x538/0x620 arch/x86/entry/common.c:296 entry_SYSCALL_64_after_hwframe+0x49/0xbe -> #2 (&sb->s_type->i_mutex_key#13){+.+.}: inode_lock include/linux/fs.h:748 [inline] __sock_release+0x86/0x2a0 net/socket.c:578 sock_close+0x15/0x20 net/socket.c:1140 __fput+0x2ce/0x890 fs/file_table.c:278 delayed_fput+0x56/0x70 fs/file_table.c:304 process_one_work+0x864/0x1570 kernel/workqueue.c:2153 worker_thread+0x64c/0x1130 kernel/workqueue.c:2296 kthread+0x33f/0x460 kernel/kthread.c:259 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415 -> #1 ((delayed_fput_work).work){+.+.}: worker_thread+0x64c/0x1130 kernel/workqueue.c:2296 kthread+0x33f/0x460 kernel/kthread.c:259 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415 -> #0 ((wq_completion)"events"){+.+.}: flush_workqueue+0x117/0x13e0 kernel/workqueue.c:2661 flush_scheduled_work include/linux/workqueue.h:599 [inline] tipc_exit_net+0x38/0x60 net/tipc/core.c:100 ops_exit_list+0xa5/0x150 net/core/net_namespace.c:153 cleanup_net+0x3b4/0x8b0 net/core/net_namespace.c:553 process_one_work+0x864/0x1570 kernel/workqueue.c:2153 worker_thread+0x64c/0x1130 kernel/workqueue.c:2296 kthread+0x33f/0x460 kernel/kthread.c:259 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415 other info that might help us debug this: Chain exists of: (wq_completion)"events" --> &sb->s_type->i_mutex_key#13 --> pernet_ops_rwsem Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(pernet_ops_rwsem); lock(&sb->s_type->i_mutex_key#13); lock(pernet_ops_rwsem); lock((wq_completion)"events"); *** DEADLOCK *** 3 locks held by kworker/u4:4/216: #0: 000000009e50802c ((wq_completion)"%s""netns"){+.+.}, at: process_one_work+0x767/0x1570 kernel/workqueue.c:2124 #1: 000000006034ce0d (net_cleanup_work){+.+.}, at: process_one_work+0x79c/0x1570 kernel/workqueue.c:2128 #2: 00000000da9fa966 (pernet_ops_rwsem){++++}, at: cleanup_net+0xa8/0x8b0 net/core/net_namespace.c:520 stack backtrace: CPU: 0 PID: 216 Comm: kworker/u4:4 Not tainted 4.19.195-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Workqueue: netns cleanup_net Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x1fc/0x2ef lib/dump_stack.c:118 print_circular_bug.constprop.0.cold+0x2d7/0x41e kernel/locking/lockdep.c:1222 check_prev_add kernel/locking/lockdep.c:1866 [inline] check_prevs_add kernel/locking/lockdep.c:1979 [inline] validate_chain kernel/locking/lockdep.c:2420 [inline] __lock_acquire+0x30c9/0x3ff0 kernel/locking/lockdep.c:3416 lock_acquire+0x170/0x3c0 kernel/locking/lockdep.c:3908 flush_workqueue+0x117/0x13e0 kernel/workqueue.c:2661 flush_scheduled_work include/linux/workqueue.h:599 [inline] tipc_exit_net+0x38/0x60 net/tipc/core.c:100 ops_exit_list+0xa5/0x150 net/core/net_namespace.c:153 cleanup_net+0x3b4/0x8b0 net/core/net_namespace.c:553 process_one_work+0x864/0x1570 kernel/workqueue.c:2153 worker_thread+0x64c/0x1130 kernel/workqueue.c:2296 kthread+0x33f/0x460 kernel/kthread.c:259 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415 team0: Device ipvlan1 failed to register rx_handler overlayfs: filesystem on './bus' not supported as upperdir overlayfs: failed to resolve './fil': -2 team0: Device ipvlan1 failed to register rx_handler overlayfs: failed to resolve './fil': -2 team0: Device ipvlan1 failed to register rx_handler overlayfs: failed to resolve './fil': -2 team0: Device ipvlan1 failed to register rx_handler team0: Device ipvlan1 failed to register rx_handler overlayfs: failed to resolve './file': -2 overlayfs: failed to resolve './file': -2 team0: Device ipvlan1 failed to register rx_handler overlayfs: failed to resolve './file': -2 overlayfs: failed to resolve './file1': -2 overlayfs: failed to resolve './file1': -2 overlayfs: unrecognized mount option "upperdir=" or missing value netlink: 28 bytes leftover after parsing attributes in process `syz-executor.0'. overlayfs: failed to resolve './file1': -2 netlink: 28 bytes leftover after parsing attributes in process `syz-executor.0'. overlayfs: unrecognized mount option "upperdir=" or missing value netlink: 28 bytes leftover after parsing attributes in process `syz-executor.0'. overlayfs: unrecognized mount option "upperdir=" or missing value netlink: 28 bytes leftover after parsing attributes in process `syz-executor.0'. netlink: 28 bytes leftover after parsing attributes in process `syz-executor.0'. overlayfs: failed to resolve './file1': -2 overlayfs: failed to resolve './file1': -2 team0: Device ipvlan1 failed to register rx_handler team0: Device ipvlan1 failed to register rx_handler netlink: 28 bytes leftover after parsing attributes in process `syz-executor.0'. team0: Device ipvlan1 failed to register rx_handler overlayfs: failed to resolve './file1': -2 overlayfs: failed to resolve './file1': -2 team0: Device ipvlan1 failed to register rx_handler overlayfs: failed to resolve './file0': -2 netlink: 8 bytes leftover after parsing attributes in process `syz-executor.0'. team0: Device ipvlan1 failed to register rx_handler overlayfs: failed to resolve './file1': -2 team0: Device ipvlan1 failed to register rx_handler overlayfs: failed to resolve './file1': -2 overlayfs: failed to resolve './file0': -2 overlayfs: failed to resolve './file0': -2 netlink: 8 bytes leftover after parsing attributes in process `syz-executor.0'. team0: Device ipvlan1 failed to register rx_handler overlayfs: failed to resolve './file1': -2 netlink: 8 bytes leftover after parsing attributes in process `syz-executor.0'. overlayfs: failed to resolve './file1': -2 team0: Device ipvlan1 failed to register rx_handler netlink: 8 bytes leftover after parsing attributes in process `syz-executor.0'. overlayfs: failed to resolve './file1': -2 overlayfs: failed to resolve './file1': -2 team0: Device ipvlan1 failed to register rx_handler overlayfs: failed to resolve './file1': -2 overlayfs: failed to resolve './file1': -2 overlayfs: failed to resolve './file1': -2 netlink: 'syz-executor.0': attribute type 16 has an invalid length. overlayfs: failed to resolve './file1': -2 overlayfs: failed to resolve './file1': -2 netlink: 'syz-executor.0': attribute type 16 has an invalid length. overlayfs: failed to resolve './file1': -2 overlayfs: failed to resolve './file1': -2 netlink: 'syz-executor.0': attribute type 16 has an invalid length. overlayfs: failed to resolve './file1': -2 overlayfs: failed to resolve './file1': -2 team0: Device ipvlan1 failed to register rx_handler overlayfs: failed to resolve './file1': -2 overlayfs: failed to resolve './file1': -2 overlayfs: failed to resolve './file1': -2 overlayfs: failed to resolve './file0': -2 overlayfs: failed to resolve './file1': -2 team0: Device ipvlan1 failed to register rx_handler overlayfs: failed to resolve './file1': -2 overlayfs: failed to resolve './file0': -2 overlayfs: failed to resolve './file1': -2 overlayfs: failed to resolve './file0': -2 overlayfs: failed to resolve './file1': -2 overlayfs: failed to resolve './file1': -2 team0: Device ipvlan1 failed to register rx_handler overlayfs: failed to resolve './file1': -2 overlayfs: failed to resolve './file1': -2 overlayfs: failed to resolve './file1': -2 team0: Device ipvlan1 failed to register rx_handler overlayfs: failed to resolve './file1': -2 team0: Device ipvlan1 failed to register rx_handler overlayfs: failed to resolve './file1': -2 team0: Device ipvlan1 failed to register rx_handler overlayfs: failed to resolve './file1': -2 nla_parse: 21 callbacks suppressed netlink: 28 bytes leftover after parsing attributes in process `syz-executor.0'. netlink: 8 bytes leftover after parsing attributes in process `syz-executor.5'. team0: Device ipvlan1 failed to register rx_handler overlayfs: failed to resolve './file1': -2 overlayfs: failed to resolve './file1': -2 overlayfs: failed to resolve './file1': -2 overlayfs: failed to resolve './file1': -2 netlink: 8 bytes leftover after parsing attributes in process `syz-executor.5'. team0: Device ipvlan1 failed to register rx_handler overlayfs: failed to resolve './file1': -2 netlink: 28 bytes leftover after parsing attributes in process `syz-executor.0'. netlink: 'syz-executor.5': attribute type 16 has an invalid length. team0: Device ipvlan1 failed to register rx_handler overlayfs: failed to resolve './file1': -2 netlink: 28 bytes leftover after parsing attributes in process `syz-executor.0'. team0: Device ipvlan1 failed to register rx_handler netlink: 'syz-executor.5': attribute type 16 has an invalid length. team0: Device ipvlan1 failed to register rx_handler overlayfs: failed to resolve './file1': -2 overlayfs: missing 'lowerdir' overlayfs: missing 'lowerdir' netlink: 28 bytes leftover after parsing attributes in process `syz-executor.0'. netlink: 'syz-executor.5': attribute type 16 has an invalid length. team0: Device ipvlan1 failed to register rx_handler overlayfs: missing 'lowerdir' overlayfs: missing 'lowerdir' overlayfs: missing 'lowerdir' netlink: 28 bytes leftover after parsing attributes in process `syz-executor.2'. team0: Device ipvlan1 failed to register rx_handler overlayfs: missing 'lowerdir' overlayfs: failed to resolve './file1': -2 overlayfs: missing 'lowerdir'