====================================================== WARNING: possible circular locking dependency detected 4.14.218-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.2/24552 is trying to acquire lock: (&event->child_mutex){+.+.}, at: [] perf_event_read_value+0x78/0x410 syzkaller/managers/linux-4-14/kernel/kernel/events/core.c:4453 but task is already holding lock: (&cpuctx_mutex){+.+.}, at: [] perf_event_ctx_lock_nested+0x14d/0x2c0 syzkaller/managers/linux-4-14/kernel/kernel/events/core.c:1241 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #5 (&cpuctx_mutex){+.+.}: __mutex_lock_common syzkaller/managers/linux-4-14/kernel/kernel/locking/mutex.c:756 [inline] __mutex_lock+0xc4/0x1310 syzkaller/managers/linux-4-14/kernel/kernel/locking/mutex.c:893 perf_event_init_cpu+0xb7/0x170 syzkaller/managers/linux-4-14/kernel/kernel/events/core.c:11250 perf_event_init+0x2cc/0x308 syzkaller/managers/linux-4-14/kernel/kernel/events/core.c:11297 start_kernel+0x46a/0x770 syzkaller/managers/linux-4-14/kernel/init/main.c:620 secondary_startup_64+0xa5/0xb0 syzkaller/managers/linux-4-14/kernel/arch/x86/kernel/head_64.S:240 -> #4 (pmus_lock){+.+.}: __mutex_lock_common syzkaller/managers/linux-4-14/kernel/kernel/locking/mutex.c:756 [inline] __mutex_lock+0xc4/0x1310 syzkaller/managers/linux-4-14/kernel/kernel/locking/mutex.c:893 perf_event_init_cpu+0x2c/0x170 syzkaller/managers/linux-4-14/kernel/kernel/events/core.c:11244 cpuhp_invoke_callback+0x1e6/0x1a80 syzkaller/managers/linux-4-14/kernel/kernel/cpu.c:184 cpuhp_up_callbacks syzkaller/managers/linux-4-14/kernel/kernel/cpu.c:572 [inline] _cpu_up+0x219/0x500 syzkaller/managers/linux-4-14/kernel/kernel/cpu.c:1144 do_cpu_up+0x9a/0x160 syzkaller/managers/linux-4-14/kernel/kernel/cpu.c:1179 smp_init+0x197/0x1ac syzkaller/managers/linux-4-14/kernel/kernel/smp.c:578 kernel_init_freeable+0x3f4/0x614 syzkaller/managers/linux-4-14/kernel/init/main.c:1068 kernel_init+0xd/0x162 syzkaller/managers/linux-4-14/kernel/init/main.c:1000 ret_from_fork+0x24/0x30 syzkaller/managers/linux-4-14/kernel/arch/x86/entry/entry_64.S:404 -> #3 (cpu_hotplug_lock.rw_sem){++++}: percpu_down_read_preempt_disable syzkaller/managers/linux-4-14/kernel/./include/linux/percpu-rwsem.h:36 [inline] percpu_down_read syzkaller/managers/linux-4-14/kernel/./include/linux/percpu-rwsem.h:59 [inline] cpus_read_lock+0x39/0xc0 syzkaller/managers/linux-4-14/kernel/kernel/cpu.c:295 static_key_slow_inc+0xe/0x20 syzkaller/managers/linux-4-14/kernel/kernel/jump_label.c:123 tracepoint_add_func+0x516/0x750 syzkaller/managers/linux-4-14/kernel/kernel/tracepoint.c:223 tracepoint_probe_register_prio syzkaller/managers/linux-4-14/kernel/kernel/tracepoint.c:283 [inline] tracepoint_probe_register+0x8c/0xc0 syzkaller/managers/linux-4-14/kernel/kernel/tracepoint.c:304 trace_event_reg+0x272/0x330 syzkaller/managers/linux-4-14/kernel/kernel/trace/trace_events.c:305 perf_trace_event_reg syzkaller/managers/linux-4-14/kernel/kernel/trace/trace_event_perf.c:122 [inline] perf_trace_event_init syzkaller/managers/linux-4-14/kernel/kernel/trace/trace_event_perf.c:197 [inline] perf_trace_init+0x424/0xa30 syzkaller/managers/linux-4-14/kernel/kernel/trace/trace_event_perf.c:221 perf_tp_event_init+0x79/0xf0 syzkaller/managers/linux-4-14/kernel/kernel/events/core.c:8138 perf_try_init_event+0x15b/0x1f0 syzkaller/managers/linux-4-14/kernel/kernel/events/core.c:9369 perf_init_event syzkaller/managers/linux-4-14/kernel/kernel/events/core.c:9407 [inline] perf_event_alloc.part.0+0xe2d/0x2640 syzkaller/managers/linux-4-14/kernel/kernel/events/core.c:9667 perf_event_alloc syzkaller/managers/linux-4-14/kernel/kernel/events/core.c:10020 [inline] SYSC_perf_event_open syzkaller/managers/linux-4-14/kernel/kernel/events/core.c:10124 [inline] SyS_perf_event_open+0x67f/0x24b0 syzkaller/managers/linux-4-14/kernel/kernel/events/core.c:10010 do_syscall_64+0x1d5/0x640 syzkaller/managers/linux-4-14/kernel/arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x46/0xbb -> #2 (tracepoints_mutex){+.+.}: __mutex_lock_common syzkaller/managers/linux-4-14/kernel/kernel/locking/mutex.c:756 [inline] __mutex_lock+0xc4/0x1310 syzkaller/managers/linux-4-14/kernel/kernel/locking/mutex.c:893 tracepoint_probe_register_prio syzkaller/managers/linux-4-14/kernel/kernel/tracepoint.c:279 [inline] tracepoint_probe_register+0x68/0xc0 syzkaller/managers/linux-4-14/kernel/kernel/tracepoint.c:304 trace_event_reg+0x272/0x330 syzkaller/managers/linux-4-14/kernel/kernel/trace/trace_events.c:305 perf_trace_event_reg syzkaller/managers/linux-4-14/kernel/kernel/trace/trace_event_perf.c:122 [inline] perf_trace_event_init syzkaller/managers/linux-4-14/kernel/kernel/trace/trace_event_perf.c:197 [inline] perf_trace_init+0x424/0xa30 syzkaller/managers/linux-4-14/kernel/kernel/trace/trace_event_perf.c:221 perf_tp_event_init+0x79/0xf0 syzkaller/managers/linux-4-14/kernel/kernel/events/core.c:8138 perf_try_init_event+0x15b/0x1f0 syzkaller/managers/linux-4-14/kernel/kernel/events/core.c:9369 perf_init_event syzkaller/managers/linux-4-14/kernel/kernel/events/core.c:9407 [inline] perf_event_alloc.part.0+0xe2d/0x2640 syzkaller/managers/linux-4-14/kernel/kernel/events/core.c:9667 perf_event_alloc syzkaller/managers/linux-4-14/kernel/kernel/events/core.c:10020 [inline] SYSC_perf_event_open syzkaller/managers/linux-4-14/kernel/kernel/events/core.c:10124 [inline] SyS_perf_event_open+0x67f/0x24b0 syzkaller/managers/linux-4-14/kernel/kernel/events/core.c:10010 do_syscall_64+0x1d5/0x640 syzkaller/managers/linux-4-14/kernel/arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x46/0xbb -> #1 (event_mutex){+.+.}: __mutex_lock_common syzkaller/managers/linux-4-14/kernel/kernel/locking/mutex.c:756 [inline] __mutex_lock+0xc4/0x1310 syzkaller/managers/linux-4-14/kernel/kernel/locking/mutex.c:893 perf_trace_destroy+0x23/0xf0 syzkaller/managers/linux-4-14/kernel/kernel/trace/trace_event_perf.c:234 _free_event+0x321/0xe20 syzkaller/managers/linux-4-14/kernel/kernel/events/core.c:4244 free_event+0x32/0x40 syzkaller/managers/linux-4-14/kernel/kernel/events/core.c:4271 perf_event_release_kernel+0x368/0x8a0 syzkaller/managers/linux-4-14/kernel/kernel/events/core.c:4415 perf_release+0x33/0x40 syzkaller/managers/linux-4-14/kernel/kernel/events/core.c:4441 __fput+0x25f/0x7a0 syzkaller/managers/linux-4-14/kernel/fs/file_table.c:210 task_work_run+0x11f/0x190 syzkaller/managers/linux-4-14/kernel/kernel/task_work.c:113 tracehook_notify_resume syzkaller/managers/linux-4-14/kernel/./include/linux/tracehook.h:191 [inline] exit_to_usermode_loop+0x1ad/0x200 syzkaller/managers/linux-4-14/kernel/arch/x86/entry/common.c:164 prepare_exit_to_usermode syzkaller/managers/linux-4-14/kernel/arch/x86/entry/common.c:199 [inline] syscall_return_slowpath syzkaller/managers/linux-4-14/kernel/arch/x86/entry/common.c:270 [inline] do_syscall_64+0x4a3/0x640 syzkaller/managers/linux-4-14/kernel/arch/x86/entry/common.c:297 entry_SYSCALL_64_after_hwframe+0x46/0xbb -> #0 (&event->child_mutex){+.+.}: lock_acquire+0x170/0x3f0 syzkaller/managers/linux-4-14/kernel/kernel/locking/lockdep.c:3998 __mutex_lock_common syzkaller/managers/linux-4-14/kernel/kernel/locking/mutex.c:756 [inline] __mutex_lock+0xc4/0x1310 syzkaller/managers/linux-4-14/kernel/kernel/locking/mutex.c:893 perf_event_read_value+0x78/0x410 syzkaller/managers/linux-4-14/kernel/kernel/events/core.c:4453 perf_read_one syzkaller/managers/linux-4-14/kernel/kernel/events/core.c:4575 [inline] __perf_read syzkaller/managers/linux-4-14/kernel/kernel/events/core.c:4626 [inline] perf_read+0x3e2/0x7c0 syzkaller/managers/linux-4-14/kernel/kernel/events/core.c:4639 do_loop_readv_writev syzkaller/managers/linux-4-14/kernel/fs/read_write.c:695 [inline] do_loop_readv_writev syzkaller/managers/linux-4-14/kernel/fs/read_write.c:682 [inline] do_iter_read+0x3eb/0x5b0 syzkaller/managers/linux-4-14/kernel/fs/read_write.c:919 vfs_readv+0xc8/0x120 syzkaller/managers/linux-4-14/kernel/fs/read_write.c:981 do_readv+0xfc/0x2c0 syzkaller/managers/linux-4-14/kernel/fs/read_write.c:1014 do_syscall_64+0x1d5/0x640 syzkaller/managers/linux-4-14/kernel/arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x46/0xbb other info that might help us debug this: Chain exists of: &event->child_mutex --> pmus_lock --> &cpuctx_mutex Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&cpuctx_mutex); lock(pmus_lock); lock(&cpuctx_mutex); lock(&event->child_mutex); *** DEADLOCK *** 1 lock held by syz-executor.2/24552: #0: (&cpuctx_mutex){+.+.}, at: [] perf_event_ctx_lock_nested+0x14d/0x2c0 syzkaller/managers/linux-4-14/kernel/kernel/events/core.c:1241 stack backtrace: CPU: 1 PID: 24552 Comm: syz-executor.2 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 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 __mutex_lock_common syzkaller/managers/linux-4-14/kernel/kernel/locking/mutex.c:756 [inline] __mutex_lock+0xc4/0x1310 syzkaller/managers/linux-4-14/kernel/kernel/locking/mutex.c:893 perf_event_read_value+0x78/0x410 syzkaller/managers/linux-4-14/kernel/kernel/events/core.c:4453 perf_read_one syzkaller/managers/linux-4-14/kernel/kernel/events/core.c:4575 [inline] __perf_read syzkaller/managers/linux-4-14/kernel/kernel/events/core.c:4626 [inline] perf_read+0x3e2/0x7c0 syzkaller/managers/linux-4-14/kernel/kernel/events/core.c:4639 do_loop_readv_writev syzkaller/managers/linux-4-14/kernel/fs/read_write.c:695 [inline] do_loop_readv_writev syzkaller/managers/linux-4-14/kernel/fs/read_write.c:682 [inline] do_iter_read+0x3eb/0x5b0 syzkaller/managers/linux-4-14/kernel/fs/read_write.c:919 vfs_readv+0xc8/0x120 syzkaller/managers/linux-4-14/kernel/fs/read_write.c:981 do_readv+0xfc/0x2c0 syzkaller/managers/linux-4-14/kernel/fs/read_write.c:1014 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:00007fdd37e7d188 EFLAGS: 00000246 ORIG_RAX: 0000000000000013 RAX: ffffffffffffffda RBX: 000000000056bf60 RCX: 0000000000465b09 RDX: 0000000000000001 RSI: 00000000200002c0 RDI: 0000000000000004 RBP: 00000000004b069f R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 000000000056bf60 R13: 00007fff3112b34f R14: 00007fdd37e7d300 R15: 0000000000022000 kauditd_printk_skb: 9 callbacks suppressed audit: type=1804 audit(1612967450.476:71): pid=24673 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.1" name="cgroup.controllers" dev="sda1" ino=16898 res=1 audit: type=1804 audit(1612967450.706:72): pid=24708 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.1" name="cgroup.controllers" dev="sda1" ino=16898 res=1 nla_parse: 15 callbacks suppressed netlink: 44 bytes leftover after parsing attributes in process `syz-executor.0'. netlink: 44 bytes leftover after parsing attributes in process `syz-executor.0'. netlink: 44 bytes leftover after parsing attributes in process `syz-executor.0'. netlink: 44 bytes leftover after parsing attributes in process `syz-executor.0'. netlink: 44 bytes leftover after parsing attributes in process `syz-executor.0'. netlink: 44 bytes leftover after parsing attributes in process `syz-executor.0'. team0: Mode changed to "broadcast" EXT4-fs (loop3): VFS: Can't find ext4 filesystem team0: Unable to change to the same mode the team is in EXT4-fs (loop3): VFS: Can't find ext4 filesystem netlink: 44 bytes leftover after parsing attributes in process `syz-executor.3'. netlink: 44 bytes leftover after parsing attributes in process `syz-executor.3'. netlink: 44 bytes leftover after parsing attributes in process `syz-executor.0'. netlink: 44 bytes leftover after parsing attributes in process `syz-executor.3'. team0: No ports can be present during mode change FAULT_INJECTION: forcing a failure. name failslab, interval 1, probability 0, space 0, times 0 CPU: 1 PID: 25014 Comm: syz-executor.2 Not tainted 4.14.218-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 ceph: device name is missing path (no : separator in +) 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] kmem_cache_alloc+0x28e/0x3c0 syzkaller/managers/linux-4-14/kernel/mm/slab.c:3550 getname_flags+0xc8/0x550 syzkaller/managers/linux-4-14/kernel/fs/namei.c:138 getname syzkaller/managers/linux-4-14/kernel/fs/namei.c:209 [inline] do_rmdir+0x84/0x3c0 syzkaller/managers/linux-4-14/kernel/fs/namei.c:3935 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:00007fdd37e7d188 EFLAGS: 00000246 ORIG_RAX: 0000000000000054 RAX: ffffffffffffffda RBX: 000000000056bf60 RCX: 0000000000465b09 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000020000000 RBP: 00007fdd37e7d1d0 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001 R13: 00007fff3112b34f R14: 00007fdd37e7d300 R15: 0000000000022000 FAULT_INJECTION: forcing a failure. name fail_page_alloc, interval 1, probability 0, space 0, times 0 CPU: 1 PID: 25062 Comm: syz-executor.2 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_fail_alloc_page syzkaller/managers/linux-4-14/kernel/mm/page_alloc.c:2898 [inline] prepare_alloc_pages syzkaller/managers/linux-4-14/kernel/mm/page_alloc.c:4131 [inline] __alloc_pages_nodemask+0x22c/0x2720 syzkaller/managers/linux-4-14/kernel/mm/page_alloc.c:4179 __alloc_pages syzkaller/managers/linux-4-14/kernel/./include/linux/gfp.h:484 [inline] __alloc_pages_node syzkaller/managers/linux-4-14/kernel/./include/linux/gfp.h:497 [inline] kmem_getpages syzkaller/managers/linux-4-14/kernel/mm/slab.c:1419 [inline] cache_grow_begin+0x91/0x630 syzkaller/managers/linux-4-14/kernel/mm/slab.c:2676 cache_alloc_refill+0x273/0x350 syzkaller/managers/linux-4-14/kernel/mm/slab.c:3043 ____cache_alloc syzkaller/managers/linux-4-14/kernel/mm/slab.c:3125 [inline] __do_cache_alloc syzkaller/managers/linux-4-14/kernel/mm/slab.c:3347 [inline] slab_alloc syzkaller/managers/linux-4-14/kernel/mm/slab.c:3382 [inline] kmem_cache_alloc+0x333/0x3c0 syzkaller/managers/linux-4-14/kernel/mm/slab.c:3550 getname_flags+0xc8/0x550 syzkaller/managers/linux-4-14/kernel/fs/namei.c:138 getname syzkaller/managers/linux-4-14/kernel/fs/namei.c:209 [inline] do_rmdir+0x84/0x3c0 syzkaller/managers/linux-4-14/kernel/fs/namei.c:3935 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:00007fdd37e7d188 EFLAGS: 00000246 ORIG_RAX: 0000000000000054 RAX: ffffffffffffffda RBX: 000000000056bf60 RCX: 0000000000465b09 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000020000000 RBP: 00007fdd37e7d1d0 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001 R13: 00007fff3112b34f R14: 00007fdd37e7d300 R15: 0000000000022000 qnx4: no qnx4 filesystem (no root dir). qnx4: no qnx4 filesystem (no root dir). batman_adv: Cannot find parent device batman_adv: batadv0: Adding interface: ip6gretap1 batman_adv: batadv0: The MTU of interface ip6gretap1 is too small (1426) to handle the transport of batman-adv packets. Packets going over this interface will be fragmented on layer2 which could impact the performance. Setting the MTU to 1560 would solve the problem. batman_adv: batadv0: Not using interface ip6gretap1 (retrying later): interface not active batman_adv: Cannot find parent device batman_adv: batadv0: Adding interface: ip6gretap2 batman_adv: batadv0: The MTU of interface ip6gretap2 is too small (1426) to handle the transport of batman-adv packets. Packets going over this interface will be fragmented on layer2 which could impact the performance. Setting the MTU to 1560 would solve the problem. batman_adv: batadv0: Not using interface ip6gretap2 (retrying later): interface not active qnx4: no qnx4 filesystem (no root dir). overlayfs: at least 2 lowerdir are needed while upperdir nonexistent qnx4: no qnx4 filesystem (no root dir). qnx4: no qnx4 filesystem (no root dir). qnx4: no qnx4 filesystem (no root dir). qnx4: no qnx4 filesystem (no root dir). print_req_error: I/O error, dev loop2, sector 0 print_req_error: I/O error, dev loop2, sector 0 qnx4: no qnx4 filesystem (no root dir). qnx4: no qnx4 filesystem (no root dir). qnx4: no qnx4 filesystem (no root dir). overlayfs: unrecognized mount option "nfs_export=on" or missing value qnx4: no qnx4 filesystem (no root dir). hpfs: bad mount options. print_req_error: I/O error, dev loop2, sector 0 qnx4: no qnx4 filesystem (no root dir). hpfs: bad mount options. qnx4: no qnx4 filesystem (no root dir). qnx6: invalid mount options. qnx6: invalid mount options. qnx4: no qnx4 filesystem (no root dir). nla_parse: 35 callbacks suppressed netlink: 44 bytes leftover after parsing attributes in process `syz-executor.2'. netlink: 44 bytes leftover after parsing attributes in process `syz-executor.4'. netlink: 44 bytes leftover after parsing attributes in process `syz-executor.2'. netlink: 44 bytes leftover after parsing attributes in process `syz-executor.4'. qnx4: no qnx4 filesystem (no root dir). befs: Unrecognized mount option "{ (@%" or missing value befs: (loop2): cannot parse mount options qnx4: no qnx4 filesystem (no root dir). befs: Unrecognized mount option "{ (@%" or missing value befs: (loop2): cannot parse mount options netlink: 44 bytes leftover after parsing attributes in process `syz-executor.0'. qnx4: no qnx4 filesystem (no root dir). netlink: 44 bytes leftover after parsing attributes in process `syz-executor.0'. qnx4: no qnx4 filesystem (no root dir). netlink: 44 bytes leftover after parsing attributes in process `syz-executor.0'. netlink: 44 bytes leftover after parsing attributes in process `syz-executor.0'. qnx4: no qnx4 filesystem (no root dir). netlink: 72 bytes leftover after parsing attributes in process `syz-executor.1'. overlayfs: unrecognized mount option "xino=on" or missing value netlink: 44 bytes leftover after parsing attributes in process `syz-executor.4'. overlayfs: unrecognized mount option "xino=on" or missing value qnx4: no qnx4 filesystem (no root dir). qnx4: no qnx4 filesystem (no root dir). qnx4: no qnx4 filesystem (no root dir). qnx4: no qnx4 filesystem (no root dir). qnx4: no qnx4 filesystem (no root dir). qnx4: no qnx4 filesystem (no root dir). qnx4: no qnx4 filesystem (no root dir). new mount options do not match the existing superblock, will be ignored qnx4: no qnx4 filesystem (no root dir). ISO 9660 Extensions: Microsoft Joliet Level 3 tmpfs: Bad mount option obj_user befs: Unrecognized mount option "{ (@%" or missing value