RDX: 10000000000003ff RSI: 00000000200023c0 RDI: 0000000000000004 RBP: 00007f916e2d51d0 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001 R13: 00007fff29d3ce5f R14: 00007f916e2d5300 R15: 0000000000022000 ====================================================== WARNING: possible circular locking dependency detected 4.14.218-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.0/7784 is trying to acquire lock: (console_owner){-.-.}, at: [] console_trylock_spinning syzkaller/managers/linux-4-14/kernel/kernel/printk/printk.c:1658 [inline] (console_owner){-.-.}, at: [] vprintk_emit+0x32a/0x620 syzkaller/managers/linux-4-14/kernel/kernel/printk/printk.c:1922 but task is already holding lock: (&(&port->lock)->rlock){-.-.}, at: [] pty_write+0xdb/0x1d0 syzkaller/managers/linux-4-14/kernel/drivers/tty/pty.c:120 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (&(&port->lock)->rlock){-.-.}: __raw_spin_lock_irqsave syzkaller/managers/linux-4-14/kernel/./include/linux/spinlock_api_smp.h:110 [inline] _raw_spin_lock_irqsave+0x8c/0xc0 syzkaller/managers/linux-4-14/kernel/kernel/locking/spinlock.c:160 tty_port_tty_get+0x1d/0x80 syzkaller/managers/linux-4-14/kernel/drivers/tty/tty_port.c:288 tty_port_default_wakeup+0x11/0x40 syzkaller/managers/linux-4-14/kernel/drivers/tty/tty_port.c:46 serial8250_tx_chars+0x3fe/0xbf0 syzkaller/managers/linux-4-14/kernel/drivers/tty/serial/8250/8250_port.c:1810 serial8250_handle_irq.part.0+0x28d/0x330 syzkaller/managers/linux-4-14/kernel/drivers/tty/serial/8250/8250_port.c:1897 serial8250_handle_irq syzkaller/managers/linux-4-14/kernel/drivers/tty/serial/8250/8250_port.c:1870 [inline] serial8250_default_handle_irq+0x8a/0x1f0 syzkaller/managers/linux-4-14/kernel/drivers/tty/serial/8250/8250_port.c:1913 serial8250_interrupt+0xf3/0x210 syzkaller/managers/linux-4-14/kernel/drivers/tty/serial/8250/8250_core.c:129 __handle_irq_event_percpu+0xee/0x7f0 syzkaller/managers/linux-4-14/kernel/kernel/irq/handle.c:147 handle_irq_event_percpu syzkaller/managers/linux-4-14/kernel/kernel/irq/handle.c:187 [inline] handle_irq_event+0xf0/0x250 syzkaller/managers/linux-4-14/kernel/kernel/irq/handle.c:204 handle_edge_irq+0x224/0xc40 syzkaller/managers/linux-4-14/kernel/kernel/irq/chip.c:770 generic_handle_irq_desc syzkaller/managers/linux-4-14/kernel/./include/linux/irqdesc.h:159 [inline] handle_irq+0x35/0x50 syzkaller/managers/linux-4-14/kernel/arch/x86/kernel/irq_64.c:87 do_IRQ+0x93/0x1d0 syzkaller/managers/linux-4-14/kernel/arch/x86/kernel/irq.c:230 ret_from_intr+0x0/0x1e native_safe_halt+0xe/0x10 syzkaller/managers/linux-4-14/kernel/./arch/x86/include/asm/irqflags.h:60 arch_safe_halt syzkaller/managers/linux-4-14/kernel/./arch/x86/include/asm/paravirt.h:94 [inline] default_idle+0x47/0x370 syzkaller/managers/linux-4-14/kernel/arch/x86/kernel/process.c:558 cpuidle_idle_call syzkaller/managers/linux-4-14/kernel/kernel/sched/idle.c:156 [inline] do_idle+0x250/0x3c0 syzkaller/managers/linux-4-14/kernel/kernel/sched/idle.c:246 cpu_startup_entry+0x14/0x20 syzkaller/managers/linux-4-14/kernel/kernel/sched/idle.c:351 start_secondary+0x4db/0x670 syzkaller/managers/linux-4-14/kernel/arch/x86/kernel/smpboot.c:272 secondary_startup_64+0xa5/0xb0 syzkaller/managers/linux-4-14/kernel/arch/x86/kernel/head_64.S:240 -> #1 (&port_lock_key){-.-.}: __raw_spin_lock_irqsave syzkaller/managers/linux-4-14/kernel/./include/linux/spinlock_api_smp.h:110 [inline] _raw_spin_lock_irqsave+0x8c/0xc0 syzkaller/managers/linux-4-14/kernel/kernel/locking/spinlock.c:160 serial8250_console_write+0x7a7/0x9d0 syzkaller/managers/linux-4-14/kernel/drivers/tty/serial/8250/8250_port.c:3253 call_console_drivers syzkaller/managers/linux-4-14/kernel/kernel/printk/printk.c:1725 [inline] console_unlock+0x99d/0xf20 syzkaller/managers/linux-4-14/kernel/kernel/printk/printk.c:2400 vprintk_emit+0x224/0x620 syzkaller/managers/linux-4-14/kernel/kernel/printk/printk.c:1923 vprintk_func+0x58/0x160 syzkaller/managers/linux-4-14/kernel/kernel/printk/printk_safe.c:401 printk+0x9e/0xbc syzkaller/managers/linux-4-14/kernel/kernel/printk/printk.c:1996 register_console+0x6f4/0xad0 syzkaller/managers/linux-4-14/kernel/kernel/printk/printk.c:2719 univ8250_console_init+0x2f/0x3a syzkaller/managers/linux-4-14/kernel/drivers/tty/serial/8250/8250_core.c:691 console_init+0x46/0x53 syzkaller/managers/linux-4-14/kernel/kernel/printk/printk.c:2800 start_kernel+0x52e/0x770 syzkaller/managers/linux-4-14/kernel/init/main.c:634 secondary_startup_64+0xa5/0xb0 syzkaller/managers/linux-4-14/kernel/arch/x86/kernel/head_64.S:240 -> #0 (console_owner){-.-.}: lock_acquire+0x170/0x3f0 syzkaller/managers/linux-4-14/kernel/kernel/locking/lockdep.c:3998 console_trylock_spinning syzkaller/managers/linux-4-14/kernel/kernel/printk/printk.c:1679 [inline] vprintk_emit+0x367/0x620 syzkaller/managers/linux-4-14/kernel/kernel/printk/printk.c:1922 vprintk_func+0x58/0x160 syzkaller/managers/linux-4-14/kernel/kernel/printk/printk_safe.c:401 printk+0x9e/0xbc syzkaller/managers/linux-4-14/kernel/kernel/printk/printk.c:1996 fail_dump syzkaller/managers/linux-4-14/kernel/lib/fault-inject.c:44 [inline] should_fail.cold+0xdf/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+0x6d/0x400 syzkaller/managers/linux-4-14/kernel/mm/slab.c:3729 kmalloc syzkaller/managers/linux-4-14/kernel/./include/linux/slab.h:493 [inline] tty_buffer_alloc+0xc0/0x270 syzkaller/managers/linux-4-14/kernel/drivers/tty/tty_buffer.c:169 __tty_buffer_request_room+0x12c/0x290 syzkaller/managers/linux-4-14/kernel/drivers/tty/tty_buffer.c:267 tty_insert_flip_string_fixed_flag+0x8b/0x210 syzkaller/managers/linux-4-14/kernel/drivers/tty/tty_buffer.c:312 tty_insert_flip_string syzkaller/managers/linux-4-14/kernel/./include/linux/tty_flip.h:37 [inline] pty_write+0x10d/0x1d0 syzkaller/managers/linux-4-14/kernel/drivers/tty/pty.c:122 n_tty_write+0x85e/0xda0 syzkaller/managers/linux-4-14/kernel/drivers/tty/n_tty.c:2356 do_tty_write syzkaller/managers/linux-4-14/kernel/drivers/tty/tty_io.c:959 [inline] tty_write+0x410/0x740 syzkaller/managers/linux-4-14/kernel/drivers/tty/tty_io.c:1043 do_loop_readv_writev syzkaller/managers/linux-4-14/kernel/fs/read_write.c:698 [inline] do_loop_readv_writev syzkaller/managers/linux-4-14/kernel/fs/read_write.c:682 [inline] do_iter_write+0x3da/0x550 syzkaller/managers/linux-4-14/kernel/fs/read_write.c:956 vfs_writev+0x125/0x290 syzkaller/managers/linux-4-14/kernel/fs/read_write.c:999 do_writev+0xfc/0x2c0 syzkaller/managers/linux-4-14/kernel/fs/read_write.c:1034 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: console_owner --> &port_lock_key --> &(&port->lock)->rlock Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&(&port->lock)->rlock); lock(&port_lock_key); lock(&(&port->lock)->rlock); lock(console_owner); *** DEADLOCK *** 5 locks held by syz-executor.0/7784: #0: (&tty->ldisc_sem){++++}, at: [] tty_ldisc_ref_wait+0x22/0x80 syzkaller/managers/linux-4-14/kernel/drivers/tty/tty_ldisc.c:284 #1: (&tty->atomic_write_lock){+.+.}, at: [] tty_write_lock syzkaller/managers/linux-4-14/kernel/drivers/tty/tty_io.c:885 [inline] #1: (&tty->atomic_write_lock){+.+.}, at: [] do_tty_write syzkaller/managers/linux-4-14/kernel/drivers/tty/tty_io.c:908 [inline] #1: (&tty->atomic_write_lock){+.+.}, at: [] tty_write+0x22d/0x740 syzkaller/managers/linux-4-14/kernel/drivers/tty/tty_io.c:1043 #2: (&tty->termios_rwsem){++++}, at: [] n_tty_write+0x18a/0xda0 syzkaller/managers/linux-4-14/kernel/drivers/tty/n_tty.c:2316 #3: (&ldata->output_lock){+.+.}, at: [] n_tty_write+0x82b/0xda0 syzkaller/managers/linux-4-14/kernel/drivers/tty/n_tty.c:2355 #4: (&(&port->lock)->rlock){-.-.}, at: [] pty_write+0xdb/0x1d0 syzkaller/managers/linux-4-14/kernel/drivers/tty/pty.c:120 stack backtrace: CPU: 1 PID: 7784 Comm: syz-executor.0 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 console_trylock_spinning syzkaller/managers/linux-4-14/kernel/kernel/printk/printk.c:1679 [inline] vprintk_emit+0x367/0x620 syzkaller/managers/linux-4-14/kernel/kernel/printk/printk.c:1922 vprintk_func+0x58/0x160 syzkaller/managers/linux-4-14/kernel/kernel/printk/printk_safe.c:401 printk+0x9e/0xbc syzkaller/managers/linux-4-14/kernel/kernel/printk/printk.c:1996 fail_dump syzkaller/managers/linux-4-14/kernel/lib/fault-inject.c:44 [inline] should_fail.cold+0xdf/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+0x6d/0x400 syzkaller/managers/linux-4-14/kernel/mm/slab.c:3729 kmalloc syzkaller/managers/linux-4-14/kernel/./include/linux/slab.h:493 [inline] tty_buffer_alloc+0xc0/0x270 syzkaller/managers/linux-4-14/kernel/drivers/tty/tty_buffer.c:169 __tty_buffer_request_room+0x12c/0x290 syzkaller/managers/linux-4-14/kernel/drivers/tty/tty_buffer.c:267 tty_insert_flip_string_fixed_flag+0x8b/0x210 syzkaller/managers/linux-4-14/kernel/drivers/tty/tty_buffer.c:312 tty_insert_flip_string syzkaller/managers/linux-4-14/kernel/./include/linux/tty_flip.h:37 [inline] pty_write+0x10d/0x1d0 syzkaller/managers/linux-4-14/kernel/drivers/tty/pty.c:122 n_tty_write+0x85e/0xda0 syzkaller/managers/linux-4-14/kernel/drivers/tty/n_tty.c:2356 do_tty_write syzkaller/managers/linux-4-14/kernel/drivers/tty/tty_io.c:959 [inline] tty_write+0x410/0x740 syzkaller/managers/linux-4-14/kernel/drivers/tty/tty_io.c:1043 do_loop_readv_writev syzkaller/managers/linux-4-14/kernel/fs/read_write.c:698 [inline] do_loop_readv_writev syzkaller/managers/linux-4-14/kernel/fs/read_write.c:682 [inline] do_iter_write+0x3da/0x550 syzkaller/managers/linux-4-14/kernel/fs/read_write.c:956 vfs_writev+0x125/0x290 syzkaller/managers/linux-4-14/kernel/fs/read_write.c:999 do_writev+0xfc/0x2c0 syzkaller/managers/linux-4-14/kernel/fs/read_write.c:1034 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:00007f916e2d5188 EFLAGS: 00000246 ORIG_RAX: 0000000000000014 RAX: ffffffffffffffda RBX: 000000000056bf60 RCX: 0000000000465b09 RDX: 10000000000003ff RSI: 00000000200023c0 RDI: 0000000000000004 RBP: 00007f916e2d51d0 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001 R13: 00007fff29d3ce5f R14: 00007f916e2d5300 R15: 0000000000022000 FAT-fs (loop3): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) audit: type=1804 audit(1613080687.307:539): pid=7800 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="ToMToU" comm="syz-executor.3" name="/root/syzkaller-testdir840067373/syzkaller.kNO9IQ/743/file0" dev="sda1" ino=16736 res=1 FAT-fs (loop2): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) audit: type=1804 audit(1613080687.307:540): pid=7800 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="ToMToU" comm="syz-executor.3" name="/root/syzkaller-testdir840067373/syzkaller.kNO9IQ/743/file0" dev="sda1" ino=16736 res=1 FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) audit: type=1800 audit(1613080687.477:541): pid=7786 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.5" name="file0" dev="loop5" ino=495 res=0 bond36 (unregistering): Releasing backup interface bridge118 FAT-fs (loop2): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) audit: type=1800 audit(1613080688.027:542): pid=7796 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.3" name="file0" dev="sda1" ino=15755 res=0 audit: type=1804 audit(1613080688.027:543): pid=7800 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.3" name="/root/syzkaller-testdir840067373/syzkaller.kNO9IQ/743/file0" dev="sda1" ino=15755 res=1 bond36 (unregistering): Released all slaves audit: type=1804 audit(1613080688.077:544): pid=7796 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="ToMToU" comm="syz-executor.3" name="/root/syzkaller-testdir840067373/syzkaller.kNO9IQ/743/file0" dev="sda1" ino=15755 res=1 audit: type=1804 audit(1613080688.077:545): pid=7800 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="ToMToU" comm="syz-executor.3" name="/root/syzkaller-testdir840067373/syzkaller.kNO9IQ/743/file0" dev="sda1" ino=15755 res=1 FAT-fs (loop3): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) audit: type=1800 audit(1613080688.137:546): pid=7856 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.2" name="file0" dev="sda1" ino=16688 res=0 FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) bond36 (uninitialized): Released all slaves bond36 (uninitialized): Released all slaves FAT-fs (loop2): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop2): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop3): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop3): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop3): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop3): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop3): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop3): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop3): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop3): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop3): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop3): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) bond37: Enslaving bridge123 as a backup interface with an up link bond37 (unregistering): Releasing backup interface bridge123 bond37 (unregistering): Released all slaves FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop3): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop3): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) bond37: Enslaving bridge124 as a backup interface with an up link bond37 (unregistering): Releasing backup interface bridge124 bond37 (unregistering): Released all slaves FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop3): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop3): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) netlink: 28 bytes leftover after parsing attributes in process `syz-executor.1'. print_req_error: I/O error, dev loop5, sector 0 FAT-fs (loop3): invalid media value (0x00) FAT-fs (loop3): Can't find a valid FAT filesystem print_req_error: I/O error, dev loop5, sector 0 netlink: 28 bytes leftover after parsing attributes in process `syz-executor.1'. FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop3): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) netlink: 44 bytes leftover after parsing attributes in process `syz-executor.1'. FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop3): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop5): Unrecognized mount option "€" or missing value print_req_error: I/O error, dev loop5, sector 0 FAT-fs (loop3): Unrecognized mount option "000000000000000000000030000000000000000000400000000000000000000004" or missing value FAT-fs (loop5): Unrecognized mount option "€" or missing value FAT-fs (loop3): Unrecognized mount option "000000000000000000000030000000000000000000400000000000000000000004" or missing value FAT-fs (loop5): bogus number of reserved sectors FAT-fs (loop5): Can't find a valid FAT filesystem FAT-fs (loop3): bogus number of reserved sectors FAT-fs (loop5): bogus number of reserved sectors FAT-fs (loop5): Can't find a valid FAT filesystem FAT-fs (loop3): Can't find a valid FAT filesystem FAT-fs (loop3): bogus number of reserved sectors FAT-fs (loop3): Can't find a valid FAT filesystem FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) netlink: 44 bytes leftover after parsing attributes in process `syz-executor.1'. FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop3): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop3): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) kauditd_printk_skb: 19 callbacks suppressed audit: type=1800 audit(1613080692.267:566): pid=8491 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.5" name="file0" dev="loop5" ino=526 res=0 FAT-fs (loop3): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) bond37: Enslaving bridge125 as a backup interface with an up link bond37 (unregistering): Releasing backup interface bridge125 audit: type=1800 audit(1613080692.487:567): pid=8535 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.5" name="file0" dev="loop5" ino=529 res=0 bond37 (unregistering): Released all slaves FAT-fs (loop3): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) bond37: Enslaving bridge126 as a backup interface with an up link netlink: 44 bytes leftover after parsing attributes in process `syz-executor.3'. audit: type=1800 audit(1613080692.767:568): pid=8617 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.5" name="file0" dev="loop5" ino=530 res=0 bond37 (unregistering): Releasing backup interface bridge126 bond37 (unregistering): Released all slaves FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) audit: type=1800 audit(1613080692.937:569): pid=8658 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.0" name="file0" dev="sda1" ino=16761 res=0 FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) audit: type=1800 audit(1613080692.967:570): pid=8658 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.0" name="file0" dev="sda1" ino=16761 res=0 audit: type=1800 audit(1613080692.987:571): pid=8686 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.0" name="file0" dev="sda1" ino=16761 res=0 audit: type=1800 audit(1613080692.987:572): pid=8658 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.0" name="file0" dev="sda1" ino=16761 res=0 FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) audit: type=1800 audit(1613080693.047:573): pid=8678 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.5" name="file0" dev="loop5" ino=531 res=0 bond37: Enslaving bridge127 as a backup interface with an up link FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) bond37 (unregistering): Releasing backup interface bridge127 audit: type=1800 audit(1613080693.257:574): pid=8736 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.5" name="file0" dev="loop5" ino=532 res=0 bond37 (unregistering): Released all slaves FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) audit: type=1800 audit(1613080693.447:575): pid=8764 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.5" name="file0" dev="loop5" ino=533 res=0 FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) bond37: Enslaving bridge128 as a backup interface with an up link FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) bond37 (unregistering): Releasing backup interface bridge128 bond37 (unregistering): Released all slaves FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop5): bogus number of reserved sectors FAT-fs (loop5): Can't find a valid FAT filesystem FAT-fs (loop5): bogus number of reserved sectors FAT-fs (loop5): Can't find a valid FAT filesystem bond37 (unregistering): Released all slaves FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) bond37 (unregistering): Released all slaves FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) bond37: Enslaving bridge129 as a backup interface with an up link FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) bond37: Enslaving bridge130 as a backup interface with a down link FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) netlink: 8 bytes leftover after parsing attributes in process `syz-executor.1'. netlink: 8 bytes leftover after parsing attributes in process `syz-executor.1'. FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) bond38: Enslaving bridge131 as a backup interface with an up link bond38 (unregistering): Releasing backup interface bridge131 bond38 (unregistering): Released all slaves FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop5): bogus number of reserved sectors FAT-fs (loop5): Can't find a valid FAT filesystem bond39: Enslaving bridge132 as a backup interface with an up link bond39 (unregistering): Releasing backup interface bridge132 bond39 (unregistering): Released all slaves FAT-fs (loop5): Unrecognized mount option "ÿÿÿÿÿÿÿÿ0xffffffffffffffff" or missing value FAT-fs (loop2): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop5): Unrecognized mount option "ÿÿÿÿÿÿÿÿ0xffffffffffffffff" or missing value FAT-fs (loop2): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) bond39: Enslaving bridge133 as a backup interface with an up link FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop2): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) vhci_hcd: Failed attach request for unsupported USB speed: UNKNOWN FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop2): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop5): invalid media value (0x93) FAT-fs (loop5): Can't find a valid FAT filesystem FAT-fs (loop5): Unrecognized mount option "./file0" or missing value vhci_hcd: Failed attach request for unsupported USB speed: UNKNOWN FAT-fs (loop2): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) bond40: Enslaving bridge134 as a backup interface with an up link bond40 (unregistering): Releasing backup interface bridge134 FAT-fs (loop5): Unrecognized mount option "00000000000000000004" or missing value FAT-fs (loop2): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) bond40 (unregistering): Released all slaves FAT-fs (loop5): Unrecognized mount option "00000000000000000004" or missing value FAT-fs (loop2): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) bond40: Enslaving bridge135 as a backup interface with an up link FAT-fs (loop2): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) bond40 (unregistering): Releasing backup interface bridge135 bond40 (unregistering): Released all slaves