====================================================== WARNING: possible circular locking dependency detected 4.14.232-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.2/13682 is trying to acquire lock: (&event->child_mutex){+.+.}, at: [] perf_event_read_value+0x78/0x410 kernel/events/core.c:4453 but task is already holding lock: (&cpuctx_mutex){+.+.}, at: [] perf_event_ctx_lock_nested+0x14d/0x2c0 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 kernel/locking/mutex.c:756 [inline] __mutex_lock+0xc4/0x1310 kernel/locking/mutex.c:893 perf_event_init_cpu+0xb7/0x170 kernel/events/core.c:11250 perf_event_init+0x2cc/0x308 kernel/events/core.c:11297 start_kernel+0x46a/0x770 init/main.c:620 secondary_startup_64+0xa5/0xb0 arch/x86/kernel/head_64.S:240 -> #4 (pmus_lock){+.+.}: __mutex_lock_common kernel/locking/mutex.c:756 [inline] __mutex_lock+0xc4/0x1310 kernel/locking/mutex.c:893 perf_event_init_cpu+0x2c/0x170 kernel/events/core.c:11244 cpuhp_invoke_callback+0x1e6/0x1a80 kernel/cpu.c:184 cpuhp_up_callbacks kernel/cpu.c:572 [inline] _cpu_up+0x219/0x500 kernel/cpu.c:1144 do_cpu_up+0x9a/0x160 kernel/cpu.c:1179 smp_init+0x197/0x1ac kernel/smp.c:578 kernel_init_freeable+0x3f4/0x614 init/main.c:1068 kernel_init+0xd/0x165 init/main.c:1000 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:404 -> #3 (cpu_hotplug_lock.rw_sem){++++}: percpu_down_read_preempt_disable include/linux/percpu-rwsem.h:36 [inline] percpu_down_read include/linux/percpu-rwsem.h:59 [inline] cpus_read_lock+0x39/0xc0 kernel/cpu.c:295 static_key_slow_inc+0xe/0x20 kernel/jump_label.c:123 tracepoint_add_func+0x747/0xa40 kernel/tracepoint.c:269 tracepoint_probe_register_prio kernel/tracepoint.c:331 [inline] tracepoint_probe_register+0x8c/0xc0 kernel/tracepoint.c:352 trace_event_reg+0x272/0x330 kernel/trace/trace_events.c:305 perf_trace_event_reg kernel/trace/trace_event_perf.c:122 [inline] perf_trace_event_init kernel/trace/trace_event_perf.c:197 [inline] perf_trace_init+0x424/0xa30 kernel/trace/trace_event_perf.c:221 perf_tp_event_init+0x79/0xf0 kernel/events/core.c:8138 perf_try_init_event+0x15b/0x1f0 kernel/events/core.c:9369 perf_init_event kernel/events/core.c:9407 [inline] perf_event_alloc.part.0+0xe2d/0x2640 kernel/events/core.c:9667 perf_event_alloc kernel/events/core.c:10020 [inline] SYSC_perf_event_open kernel/events/core.c:10124 [inline] SyS_perf_event_open+0x67f/0x24b0 kernel/events/core.c:10010 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x46/0xbb -> #2 (tracepoints_mutex){+.+.}: __mutex_lock_common kernel/locking/mutex.c:756 [inline] __mutex_lock+0xc4/0x1310 kernel/locking/mutex.c:893 tracepoint_probe_register_prio kernel/tracepoint.c:327 [inline] tracepoint_probe_register+0x68/0xc0 kernel/tracepoint.c:352 trace_event_reg+0x272/0x330 kernel/trace/trace_events.c:305 perf_trace_event_reg kernel/trace/trace_event_perf.c:122 [inline] perf_trace_event_init kernel/trace/trace_event_perf.c:197 [inline] perf_trace_init+0x424/0xa30 kernel/trace/trace_event_perf.c:221 perf_tp_event_init+0x79/0xf0 kernel/events/core.c:8138 perf_try_init_event+0x15b/0x1f0 kernel/events/core.c:9369 perf_init_event kernel/events/core.c:9407 [inline] perf_event_alloc.part.0+0xe2d/0x2640 kernel/events/core.c:9667 perf_event_alloc kernel/events/core.c:10020 [inline] SYSC_perf_event_open kernel/events/core.c:10124 [inline] SyS_perf_event_open+0x67f/0x24b0 kernel/events/core.c:10010 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x46/0xbb -> #1 (event_mutex){+.+.}: __mutex_lock_common kernel/locking/mutex.c:756 [inline] __mutex_lock+0xc4/0x1310 kernel/locking/mutex.c:893 perf_trace_destroy+0x23/0xf0 kernel/trace/trace_event_perf.c:234 _free_event+0x321/0xe20 kernel/events/core.c:4244 free_event+0x32/0x40 kernel/events/core.c:4271 perf_event_release_kernel+0x368/0x8a0 kernel/events/core.c:4415 perf_release+0x33/0x40 kernel/events/core.c:4441 __fput+0x25f/0x7a0 fs/file_table.c:210 task_work_run+0x11f/0x190 kernel/task_work.c:113 tracehook_notify_resume include/linux/tracehook.h:191 [inline] exit_to_usermode_loop+0x1ad/0x200 arch/x86/entry/common.c:164 prepare_exit_to_usermode arch/x86/entry/common.c:199 [inline] syscall_return_slowpath arch/x86/entry/common.c:270 [inline] do_syscall_64+0x4a3/0x640 arch/x86/entry/common.c:297 entry_SYSCALL_64_after_hwframe+0x46/0xbb -> #0 (&event->child_mutex){+.+.}: lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3998 __mutex_lock_common kernel/locking/mutex.c:756 [inline] __mutex_lock+0xc4/0x1310 kernel/locking/mutex.c:893 perf_event_read_value+0x78/0x410 kernel/events/core.c:4453 perf_read_one kernel/events/core.c:4575 [inline] __perf_read kernel/events/core.c:4626 [inline] perf_read+0x3e2/0x7c0 kernel/events/core.c:4639 do_loop_readv_writev fs/read_write.c:695 [inline] do_loop_readv_writev fs/read_write.c:682 [inline] do_iter_read+0x3eb/0x5b0 fs/read_write.c:919 vfs_readv+0xc8/0x120 fs/read_write.c:981 do_readv+0xfc/0x2c0 fs/read_write.c:1014 do_syscall_64+0x1d5/0x640 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/13682: #0: (&cpuctx_mutex){+.+.}, at: [] perf_event_ctx_lock_nested+0x14d/0x2c0 kernel/events/core.c:1241 stack backtrace: CPU: 1 PID: 13682 Comm: syz-executor.2 Not tainted 4.14.232-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: __dump_stack lib/dump_stack.c:17 [inline] dump_stack+0x1b2/0x281 lib/dump_stack.c:58 print_circular_bug.constprop.0.cold+0x2d7/0x41e kernel/locking/lockdep.c:1258 check_prev_add kernel/locking/lockdep.c:1905 [inline] check_prevs_add kernel/locking/lockdep.c:2022 [inline] validate_chain kernel/locking/lockdep.c:2464 [inline] __lock_acquire+0x2e0e/0x3f20 kernel/locking/lockdep.c:3491 lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3998 __mutex_lock_common kernel/locking/mutex.c:756 [inline] __mutex_lock+0xc4/0x1310 kernel/locking/mutex.c:893 perf_event_read_value+0x78/0x410 kernel/events/core.c:4453 perf_read_one kernel/events/core.c:4575 [inline] __perf_read kernel/events/core.c:4626 [inline] perf_read+0x3e2/0x7c0 kernel/events/core.c:4639 do_loop_readv_writev fs/read_write.c:695 [inline] do_loop_readv_writev fs/read_write.c:682 [inline] do_iter_read+0x3eb/0x5b0 fs/read_write.c:919 vfs_readv+0xc8/0x120 fs/read_write.c:981 do_readv+0xfc/0x2c0 fs/read_write.c:1014 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x46/0xbb RIP: 0033:0x4665f9 RSP: 002b:00007fd68db0d188 EFLAGS: 00000246 ORIG_RAX: 0000000000000013 RAX: ffffffffffffffda RBX: 000000000056bf60 RCX: 00000000004665f9 RDX: 0000000000000001 RSI: 00000000200002c0 RDI: 0000000000000005 RBP: 00000000004bfce1 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 000000000056bf60 R13: 00007ffd581729ff R14: 00007fd68db0d300 R15: 0000000000022000 print_req_error: 144 callbacks suppressed print_req_error: I/O error, dev loop3, sector 264064 print_req_error: I/O error, dev loop3, sector 264064 buffer_io_error: 119 callbacks suppressed Buffer I/O error on dev loop3p4, logical block 33008, async page read usb usb4: usbfs: process 13742 (syz-executor.5) did not claim interface 0 before use print_req_error: I/O error, dev loop3, sector 70 print_req_error: I/O error, dev loop3, sector 264064 print_req_error: I/O error, dev loop3, sector 70 Buffer I/O error on dev loop3p2, logical block 0, async page read print_req_error: I/O error, dev loop3, sector 264064 Buffer I/O error on dev loop3p4, logical block 33008, async page read print_req_error: I/O error, dev loop3, sector 70 Buffer I/O error on dev loop3p2, logical block 0, async page read print_req_error: I/O error, dev loop3, sector 70 Buffer I/O error on dev loop3p2, logical block 0, async page read print_req_error: I/O error, dev loop3, sector 70 Buffer I/O error on dev loop3p2, logical block 0, async page read print_req_error: I/O error, dev loop3, sector 70 Buffer I/O error on dev loop3p2, logical block 0, async page read Buffer I/O error on dev loop3p2, logical block 0, async page read Buffer I/O error on dev loop3p2, logical block 0, async page read Buffer I/O error on dev loop3p2, logical block 0, async page read Cannot find set identified by id 0 to match usb usb4: usbfs: process 13767 (syz-executor.5) did not claim interface 0 before use Cannot find set identified by id 0 to match Cannot find set identified by id 0 to match usb usb4: usbfs: process 13796 (syz-executor.5) did not claim interface 0 before use hfs: unable to change codepage Cannot find set identified by id 0 to match hfs: unable to parse mount options usb usb4: usbfs: process 13816 (syz-executor.5) did not claim interface 0 before use Cannot find set identified by id 0 to match hfs: unable to change codepage hfs: unable to parse mount options hfs: unable to change codepage hfs: unable to parse mount options EXT4-fs (loop2): mounted filesystem without journal. Opts: ,errors=continue netlink: 24 bytes leftover after parsing attributes in process `syz-executor.0'. hfs: unable to change codepage hfs: unable to parse mount options EXT4-fs error (device loop2): ext4_validate_block_bitmap:405: comm syz-executor.2: bg 0: block 2: invalid block bitmap netlink: 4 bytes leftover after parsing attributes in process `syz-executor.5'. EXT4-fs (loop2): Delayed block allocation failed for inode 17 at logical offset 32799 with max blocks 37 with error 117 netlink: 4 bytes leftover after parsing attributes in process `syz-executor.5'. EXT4-fs (loop2): This should not happen!! Data will be lost 8021q: adding VLAN 0 to HW filter on device ipvlan2 hfs: unable to change codepage hfs: unable to parse mount options netlink: 24 bytes leftover after parsing attributes in process `syz-executor.0'. 8021q: adding VLAN 0 to HW filter on device ipvlan2 EXT4-fs (loop2): mounted filesystem without journal. Opts: ,errors=continue EXT4-fs error (device loop2): ext4_validate_block_bitmap:405: comm syz-executor.2: bg 0: block 2: invalid block bitmap EXT4-fs (loop2): Delayed block allocation failed for inode 17 at logical offset 32799 with max blocks 37 with error 117 EXT4-fs (loop2): This should not happen!! Data will be lost netlink: 24 bytes leftover after parsing attributes in process `syz-executor.0'. 8021q: adding VLAN 0 to HW filter on device ipvlan2 sg_write: data in/out 167162/56 bytes for SCSI command 0xa1-- guessing data in; program syz-executor.4 not setting count and/or reply_len properly EXT4-fs (loop2): mounted filesystem without journal. Opts: ,errors=continue netlink: 24 bytes leftover after parsing attributes in process `syz-executor.0'. EXT4-fs error (device loop2): ext4_validate_block_bitmap:405: comm syz-executor.2: bg 0: block 2: invalid block bitmap kauditd_printk_skb: 2 callbacks suppressed audit: type=1800 audit(1620479614.779:30): pid=14044 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.1" name="file0" dev="sda1" ino=14207 res=0 overlayfs: upperdir is in-use by another mount, accessing files from both mounts will result in undefined behavior. 8021q: adding VLAN 0 to HW filter on device ipvlan2 overlayfs: workdir is in-use by another mount, accessing files from both mounts will result in undefined behavior. EXT4-fs (loop2): Delayed block allocation failed for inode 17 at logical offset 32799 with max blocks 37 with error 117 overlayfs: upperdir is in-use by another mount, mount with '-o index=off' to override exclusive upperdir protection. audit: type=1804 audit(1620479614.809:31): pid=14044 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.1" name="/root/syzkaller-testdir427707742/syzkaller.Bf2yV4/126/file0" dev="sda1" ino=14207 res=1 overlayfs: upperdir is in-use by another mount, accessing files from both mounts will result in undefined behavior. EXT4-fs (loop2): This should not happen!! Data will be lost overlayfs: workdir is in-use by another mount, accessing files from both mounts will result in undefined behavior. audit: type=1804 audit(1620479614.809:32): pid=14044 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="ToMToU" comm="syz-executor.1" name="/root/syzkaller-testdir427707742/syzkaller.Bf2yV4/126/file0" dev="sda1" ino=14207 res=1 overlayfs: maximum fs stacking depth exceeded EXT4-fs (loop2): mounted filesystem without journal. Opts: ,errors=continue EXT4-fs error (device loop2): ext4_validate_block_bitmap:405: comm syz-executor.2: bg 0: block 2: invalid block bitmap EXT4-fs (loop2): Delayed block allocation failed for inode 17 at logical offset 32799 with max blocks 29 with error 117 EXT4-fs (loop2): This should not happen!! Data will be lost netlink: 24 bytes leftover after parsing attributes in process `syz-executor.0'. 8021q: adding VLAN 0 to HW filter on device ipvlan2 audit: type=1804 audit(1620479615.589:33): pid=14059 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="ToMToU" comm="syz-executor.1" name="/root/syzkaller-testdir427707742/syzkaller.Bf2yV4/126/file0" dev="sda1" ino=14207 res=1 audit: type=1804 audit(1620479615.589:34): pid=14129 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.1" name="/root/syzkaller-testdir427707742/syzkaller.Bf2yV4/126/file0" dev="sda1" ino=14207 res=1 audit: type=1804 audit(1620479615.589:35): pid=14130 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="ToMToU" comm="syz-executor.1" name="/root/syzkaller-testdir427707742/syzkaller.Bf2yV4/126/file0" dev="sda1" ino=14207 res=1 audit: type=1800 audit(1620479615.689:36): pid=14139 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.1" name="file0" dev="sda1" ino=14243 res=0 audit: type=1804 audit(1620479615.729:37): pid=14139 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.1" name="/root/syzkaller-testdir427707742/syzkaller.Bf2yV4/127/file0" dev="sda1" ino=14243 res=1 audit: type=1804 audit(1620479615.729:38): pid=14139 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="ToMToU" comm="syz-executor.1" name="/root/syzkaller-testdir427707742/syzkaller.Bf2yV4/127/file0" dev="sda1" ino=14243 res=1 netlink: 24 bytes leftover after parsing attributes in process `syz-executor.2'. JFS: charset not found JFS: charset not found sctp: [Deprecated]: syz-executor.4 (pid 14233) Use of int in max_burst socket option deprecated. Use struct sctp_assoc_value instead audit: type=1800 audit(1620479616.449:39): pid=14237 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.1" name="file0" dev="sda1" ino=14262 res=0 sctp: [Deprecated]: syz-executor.4 (pid 14244) Use of int in maxseg socket option. Use struct sctp_assoc_value instead sctp: [Deprecated]: syz-executor.4 (pid 14244) Use of int in max_burst socket option deprecated. Use struct sctp_assoc_value instead sctp: [Deprecated]: syz-executor.4 (pid 14233) Use of int in maxseg socket option. Use struct sctp_assoc_value instead [EXT4 FS bs=1024, gc=1, bpg=8192, ipg=32, mo=a802c018, mo2=0006] System zones: 1-2, 19-19, 35-38, 46-46 EXT4-fs (loop5): mounted filesystem without journal. Opts: ,errors=continue sctp: [Deprecated]: syz-executor.4 (pid 14297) Use of int in max_burst socket option deprecated. Use struct sctp_assoc_value instead sctp: [Deprecated]: syz-executor.4 (pid 14297) Use of int in maxseg socket option. Use struct sctp_assoc_value instead sctp: [Deprecated]: syz-executor.4 (pid 14344) Use of int in max_burst socket option deprecated. Use struct sctp_assoc_value instead sctp: [Deprecated]: syz-executor.4 (pid 14344) Use of int in maxseg socket option. Use struct sctp_assoc_value instead sctp: [Deprecated]: syz-executor.4 (pid 14367) Use of int in max_burst socket option deprecated. Use struct sctp_assoc_value instead sctp: [Deprecated]: syz-executor.4 (pid 14367) Use of int in maxseg socket option. Use struct sctp_assoc_value instead XFS (loop5): sunit and swidth must be specified together XFS (loop5): sunit and swidth must be specified together print_req_error: 268 callbacks suppressed print_req_error: I/O error, dev loop3, sector 70 print_req_error: I/O error, dev loop3, sector 264064 print_req_error: I/O error, dev loop3, sector 264064 buffer_io_error: 221 callbacks suppressed Buffer I/O error on dev loop3p4, logical block 33008, async page read print_req_error: I/O error, dev loop3, sector 70 Buffer I/O error on dev loop3p2, logical block 0, async page read print_req_error: I/O error, dev loop3, sector 70 Buffer I/O error on dev loop3p2, logical block 0, async page read print_req_error: I/O error, dev loop3, sector 70 Buffer I/O error on dev loop3p2, logical block 0, async page read print_req_error: I/O error, dev loop3, sector 70 Buffer I/O error on dev loop3p2, logical block 0, async page read print_req_error: I/O error, dev loop3, sector 70 Buffer I/O error on dev loop3p2, logical block 0, async page read print_req_error: I/O error, dev loop3, sector 70 Buffer I/O error on dev loop3p2, logical block 0, async page read print_req_error: I/O error, dev loop3, sector 70 Buffer I/O error on dev loop3p2, logical block 0, async page read Buffer I/O error on dev loop3p2, logical block 0, async page read Buffer I/O error on dev loop3p2, logical block 0, async page read EXT4-fs (sda1): Cannot specify journal on remount overlayfs: filesystem on './file0' not supported as upperdir EXT4-fs (sda1): Cannot specify journal on remount EXT4-fs (sda1): Cannot specify journal on remount EXT4-fs (sda1): Cannot specify journal on remount netlink: 24 bytes leftover after parsing attributes in process `syz-executor.2'. EXT4-fs (sda1): Cannot specify journal on remount netlink: 8 bytes leftover after parsing attributes in process `syz-executor.1'. IPVS: ftp: loaded support on port[0] = 21 __ntfs_error: 8 callbacks suppressed ntfs: (device loop2): parse_options(): The uid option requires an argument. new mount options do not match the existing superblock, will be ignored ntfs: (device loop2): parse_options(): The uid option requires an argument. overlayfs: filesystem on './bus' not supported as upperdir ntfs: (device loop2): parse_options(): The uid option requires an argument. UDF-fs: error (device loop4): udf_read_tagged: read failed, block=256, location=256 UDF-fs: error (device loop4): udf_read_tagged: read failed, block=512, location=512 UDF-fs: warning (device loop4): udf_load_vrs: No anchor found overlayfs: fs on 'file0' does not support file handles, falling back to index=off. UDF-fs: Scanning with blocksize 512 failed UDF-fs: error (device loop4): udf_read_tagged: read failed, block=256, location=256 UDF-fs: error (device loop4): udf_read_tagged: read failed, block=512, location=512 overlayfs: fs on 'file0' does not support file handles, falling back to index=off. UDF-fs: warning (device loop4): udf_load_vrs: No anchor found UDF-fs: Scanning with blocksize 1024 failed UDF-fs: error (device loop4): udf_read_tagged: read failed, block=256, location=256 UDF-fs: error (device loop4): udf_read_tagged: read failed, block=512, location=512 UDF-fs: warning (device loop4): udf_load_vrs: No anchor found UDF-fs: Scanning with blocksize 2048 failed UDF-fs: error (device loop4): udf_read_tagged: read failed, block=256, location=256 UDF-fs: error (device loop4): udf_read_tagged: read failed, block=512, location=512 UDF-fs: warning (device loop4): udf_load_vrs: No anchor found UDF-fs: Scanning with blocksize 4096 failed UDF-fs: warning (device loop4): udf_fill_super: No partition found (1) UDF-fs: error (device loop4): udf_read_tagged: read failed, block=256, location=256 UDF-fs: error (device loop4): udf_read_tagged: read failed, block=512, location=512 UDF-fs: warning (device loop4): udf_load_vrs: No anchor found UDF-fs: Scanning with blocksize 512 failed UDF-fs: error (device loop4): udf_read_tagged: read failed, block=256, location=256 UDF-fs: error (device loop4): udf_read_tagged: read failed, block=512, location=512 UDF-fs: warning (device loop4): udf_load_vrs: No anchor found UDF-fs: Scanning with blocksize 1024 failed UDF-fs: error (device loop4): udf_read_tagged: read failed, block=256, location=256 UDF-fs: error (device loop4): udf_read_tagged: read failed, block=512, location=512 UDF-fs: warning (device loop4): udf_load_vrs: No anchor found UDF-fs: Scanning with blocksize 2048 failed UDF-fs: error (device loop4): udf_read_tagged: read failed, block=256, location=256 UDF-fs: error (device loop4): udf_read_tagged: read failed, block=512, location=512 UDF-fs: warning (device loop4): udf_load_vrs: No anchor found UDF-fs: Scanning with blocksize 4096 failed UDF-fs: warning (device loop4): udf_fill_super: No partition found (1) ipt_ECN: unsupported ECN operation 38 audit: type=1804 audit(1620479620.769:46): pid=14789 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.1" name="/root/syzkaller-testdir427707742/syzkaller.Bf2yV4/143/file0" dev="sda1" ino=14305 res=1 overlayfs: './file0' not a directory ipt_ECN: unsupported ECN operation 38 audit: type=1804 audit(1620479620.779:47): pid=14786 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.2" name="/root/syzkaller-testdir633297961/syzkaller.ur6Usc/157/bus/file0" dev="sda1" ino=14302 res=1 audit: type=1804 audit(1620479620.859:48): pid=14802 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.2" name="/root/syzkaller-testdir633297961/syzkaller.ur6Usc/157/bus/bus/file0" dev="sda1" ino=14291 res=1 attempt to access beyond end of device cannot load conntrack support for proto=2 loop3p4: rw=0, want=264072, limit=262159 attempt to access beyond end of device loop3p4: rw=0, want=264072, limit=262159 audit: type=1804 audit(1620479620.859:49): pid=14786 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="ToMToU" comm="syz-executor.2" name="/root/syzkaller-testdir633297961/syzkaller.ur6Usc/157/bus/bus/file0" dev="sda1" ino=14291 res=1 ISO 9660 Extensions: Microsoft Joliet Level 0 Unable to read rock-ridge attributes ISO 9660 Extensions: Microsoft Joliet Level 0 Unable to read rock-ridge attributes ISO 9660 Extensions: Microsoft Joliet Level 0 Unable to read rock-ridge attributes ISO 9660 Extensions: Microsoft Joliet Level 0 Unable to read rock-ridge attributes