FAULT_INJECTION: forcing a failure. name failslab, interval 1, probability 0, space 0, times 0 ttyprintk ttyprintk: tty_port_close_start: tty->count = 1 port count = 2 ====================================================== WARNING: possible circular locking dependency detected 4.19.186-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.0/20730 is trying to acquire lock: 000000009da309bf (console_owner){-.-.}, at: console_trylock_spinning kernel/printk/printk.c:1697 [inline] 000000009da309bf (console_owner){-.-.}, at: vprintk_emit+0x3fe/0x740 kernel/printk/printk.c:1964 but task is already holding lock: 000000001981a505 (&(&port->lock)->rlock){-.-.}, at: tty_port_close_start.part.0+0x28/0x540 drivers/tty/tty_port.c:574 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (&(&port->lock)->rlock){-.-.}: tty_port_tty_get+0x1d/0x80 drivers/tty/tty_port.c:289 tty_port_default_wakeup+0x11/0x40 drivers/tty/tty_port.c:47 serial8250_tx_chars+0x490/0xaf0 drivers/tty/serial/8250/8250_port.c:1806 serial8250_handle_irq.part.0+0x31f/0x3d0 drivers/tty/serial/8250/8250_port.c:1893 serial8250_handle_irq drivers/tty/serial/8250/8250_port.c:1866 [inline] serial8250_default_handle_irq+0xae/0x220 drivers/tty/serial/8250/8250_port.c:1909 serial8250_interrupt+0x101/0x240 drivers/tty/serial/8250/8250_core.c:125 __handle_irq_event_percpu+0x27e/0x8e0 kernel/irq/handle.c:149 handle_irq_event_percpu kernel/irq/handle.c:189 [inline] handle_irq_event+0x102/0x290 kernel/irq/handle.c:206 handle_edge_irq+0x260/0xcf0 kernel/irq/chip.c:797 generic_handle_irq_desc include/linux/irqdesc.h:155 [inline] handle_irq+0x35/0x50 arch/x86/kernel/irq_64.c:87 do_IRQ+0x93/0x1c0 arch/x86/kernel/irq.c:246 ret_from_intr+0x0/0x1e arch_local_irq_restore arch/x86/include/asm/paravirt.h:789 [inline] __raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:160 [inline] _raw_spin_unlock_irqrestore+0xa3/0xe0 kernel/locking/spinlock.c:184 spin_unlock_irqrestore include/linux/spinlock.h:384 [inline] uart_write+0x3bb/0x6f0 drivers/tty/serial/serial_core.c:612 do_output_char+0x5de/0x850 drivers/tty/n_tty.c:445 process_output drivers/tty/n_tty.c:512 [inline] n_tty_write+0x46e/0xff0 drivers/tty/n_tty.c:2343 do_tty_write drivers/tty/tty_io.c:960 [inline] tty_write+0x496/0x810 drivers/tty/tty_io.c:1044 redirected_tty_write+0xaa/0xb0 drivers/tty/tty_io.c:1065 do_loop_readv_writev fs/read_write.c:704 [inline] do_loop_readv_writev fs/read_write.c:688 [inline] do_iter_write+0x461/0x5d0 fs/read_write.c:962 vfs_writev+0x153/0x2e0 fs/read_write.c:1005 do_writev+0x136/0x330 fs/read_write.c:1040 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe -> #1 (&port_lock_key){-.-.}: serial8250_console_write+0x89b/0xad0 drivers/tty/serial/8250/8250_port.c:3270 call_console_drivers kernel/printk/printk.c:1764 [inline] console_unlock+0xbb6/0x1110 kernel/printk/printk.c:2460 vprintk_emit+0x2d1/0x740 kernel/printk/printk.c:1965 vprintk_func+0x79/0x180 kernel/printk/printk_safe.c:405 printk+0xba/0xed kernel/printk/printk.c:2040 register_console+0x87f/0xc90 kernel/printk/printk.c:2776 univ8250_console_init+0x3a/0x46 drivers/tty/serial/8250/8250_core.c:684 console_init+0x4cb/0x718 kernel/printk/printk.c:2862 start_kernel+0x686/0x911 init/main.c:659 secondary_startup_64+0xa4/0xb0 arch/x86/kernel/head_64.S:243 -> #0 (console_owner){-.-.}: console_trylock_spinning kernel/printk/printk.c:1718 [inline] vprintk_emit+0x43b/0x740 kernel/printk/printk.c:1964 vprintk_func+0x79/0x180 kernel/printk/printk_safe.c:405 printk+0xba/0xed kernel/printk/printk.c:2040 tty_port_close_start.part.0+0x4f3/0x540 drivers/tty/tty_port.c:576 tty_port_close_start drivers/tty/tty_port.c:648 [inline] tty_port_close+0x46/0x160 drivers/tty/tty_port.c:641 tty_release+0x45e/0x1210 drivers/tty/tty_io.c:1678 __fput+0x2ce/0x890 fs/file_table.c:278 task_work_run+0x148/0x1c0 kernel/task_work.c:113 tracehook_notify_resume include/linux/tracehook.h:193 [inline] exit_to_usermode_loop+0x251/0x2a0 arch/x86/entry/common.c:167 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 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 *** 2 locks held by syz-executor.0/20730: #0: 00000000bc6060f3 (&tty->legacy_mutex){+.+.}, at: tty_lock+0x6a/0xa0 drivers/tty/tty_mutex.c:19 #1: 000000001981a505 (&(&port->lock)->rlock){-.-.}, at: tty_port_close_start.part.0+0x28/0x540 drivers/tty/tty_port.c:574 stack backtrace: CPU: 0 PID: 20730 Comm: syz-executor.0 Not tainted 4.19.186-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 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:1221 check_prev_add kernel/locking/lockdep.c:1865 [inline] check_prevs_add kernel/locking/lockdep.c:1978 [inline] validate_chain kernel/locking/lockdep.c:2419 [inline] __lock_acquire+0x30c9/0x3ff0 kernel/locking/lockdep.c:3415 lock_acquire+0x170/0x3c0 kernel/locking/lockdep.c:3907 console_trylock_spinning kernel/printk/printk.c:1718 [inline] vprintk_emit+0x43b/0x740 kernel/printk/printk.c:1964 vprintk_func+0x79/0x180 kernel/printk/printk_safe.c:405 printk+0xba/0xed kernel/printk/printk.c:2040 tty_port_close_start.part.0+0x4f3/0x540 drivers/tty/tty_port.c:576 tty_port_close_start drivers/tty/tty_port.c:648 [inline] tty_port_close+0x46/0x160 drivers/tty/tty_port.c:641 tty_release+0x45e/0x1210 drivers/tty/tty_io.c:1678 __fput+0x2ce/0x890 fs/file_table.c:278 task_work_run+0x148/0x1c0 kernel/task_work.c:113 tracehook_notify_resume include/linux/tracehook.h:193 [inline] exit_to_usermode_loop+0x251/0x2a0 arch/x86/entry/common.c:167 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 RIP: 0033:0x41926b Code: 0f 05 48 3d 00 f0 ff ff 77 45 c3 0f 1f 40 00 48 83 ec 18 89 7c 24 0c e8 63 fc ff ff 8b 7c 24 0c 41 89 c0 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 35 44 89 c7 89 44 24 0c e8 a1 fc ff ff 8b 44 RSP: 002b:00007ffd178d7670 EFLAGS: 00000293 ORIG_RAX: 0000000000000003 RAX: 0000000000000000 RBX: 0000000000000004 RCX: 000000000041926b RDX: 0000000000570120 RSI: 0000000000000081 RDI: 0000000000000003 RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000570120 R13: 00007ffd178d7790 R14: 000000000056bf60 R15: 0000000000054494 overlayfs: unrecognized mount option "upp^rdir=./file1" or missing value CPU: 0 PID: 20742 Comm: syz-executor.5 Not tainted 4.19.186-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x1fc/0x2ef lib/dump_stack.c:118 fail_dump lib/fault-inject.c:51 [inline] should_fail.cold+0xa/0xf lib/fault-inject.c:149 __should_failslab+0x115/0x180 mm/failslab.c:32 should_failslab+0x5/0x10 mm/slab_common.c:1588 slab_pre_alloc_hook mm/slab.h:424 [inline] slab_alloc_node mm/slab.c:3304 [inline] kmem_cache_alloc_node_trace+0x244/0x3b0 mm/slab.c:3666 Bluetooth: hci0: command 0x0406 tx timeout __do_kmalloc_node mm/slab.c:3688 [inline] __kmalloc_node_track_caller+0x38/0x70 mm/slab.c:3703 __kmalloc_reserve net/core/skbuff.c:137 [inline] __alloc_skb+0xae/0x560 net/core/skbuff.c:205 alloc_skb include/linux/skbuff.h:995 [inline] sock_wmalloc+0xd0/0x120 net/core/sock.c:1942 pppoe_sendmsg+0x2ac/0x710 drivers/net/ppp/pppoe.c:874 sock_sendmsg_nosec net/socket.c:622 [inline] sock_sendmsg+0xc3/0x120 net/socket.c:632 ___sys_sendmsg+0x3b3/0x8e0 net/socket.c:2115 __sys_sendmmsg+0x195/0x470 net/socket.c:2210 __do_sys_sendmmsg net/socket.c:2239 [inline] __se_sys_sendmmsg net/socket.c:2236 [inline] __x64_sys_sendmmsg+0x99/0x100 net/socket.c:2236 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe RIP: 0033:0x466459 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 bc ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fa652458188 EFLAGS: 00000246 ORIG_RAX: 0000000000000133 RAX: ffffffffffffffda RBX: 000000000056bf60 RCX: 0000000000466459 RDX: 04000000000000eb RSI: 000000002000d180 RDI: 0000000000000004 RBP: 00007fa6524581d0 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000002 R13: 00007fff90bfb75f R14: 00007fa652458300 R15: 0000000000022000 overlayfs: unrecognized mount option "obj_role=overlay" or missing value overlayfs: unrecognized mount option "obj_role=overlay" or missing value overlayfs: fs on './bus' does not support file handles, falling back to index=off,nfs_export=off. overlayfs: "xino" feature enabled using 1 upper inode bits. overlayfs: upperdir is in-use as upperdir/workdir of another mount, mount with '-o index=off' to override exclusive upperdir protection. overlayfs: unrecognized mount option "xioo=on" or missing value overlayfs: fs on './bus' does not support file handles, falling back to index=off,nfs_export=off. overlayfs: "xino" feature enabled using 1 upper inode bits. overlayfs: upperdir is in-use as upperdir/workdir of another mount, mount with '-o index=off' to override exclusive upperdir protection. overlayfs: fs on './bus' does not support file handles, falling back to index=off,nfs_export=off. overlayfs: "xino" feature enabled using 1 upper inode bits. overlayfs: upperdir is in-use as upperdir/workdir of another mount, mount with '-o index=off' to override exclusive upperdir protection. overlayfs: unrecognized mount option "upperâ]" or missing value overlayfs: unrecognized mount option "upperâ]" or missing value overlayfs: fs on './bus' does not support file handles, falling back to index=off,nfs_export=off. overlayfs: "xino" feature enabled using 1 upper inode bits. overlayfs: upperdir is in-use as upperdir/workdir of another mount, mount with '-o index=off' to override exclusive upperdir protection. overlayfs: fs on './bus' does not support file handles, falling back to index=off,nfs_export=off. overlayfs: "xino" feature enabled using 1 upper inode bits. overlayfs: upperdir is in-use as upperdir/workdir of another mount, mount with '-o index=off' to override exclusive upperdir protection. overlayfs: fs on './bus' does not support file handles, falling back to index=off,nfs_export=off. overlayfs: "xino" feature enabled using 1 upper inode bits. overlayfs: upperdir is in-use as upperdir/workdir of another mount, mount with '-o index=off' to override exclusive upperdir protection. overlayfs: fs on './bus' does not support file handles, falling back to index=off,nfs_export=off. overlayfs: "xino" feature enabled using 1 upper inode bits. overlayfs: upperdir is in-use as upperdir/workdir of another mount, mount with '-o index=off' to override exclusive upperdir protection. overlayfs: fs on './bus' does not support file handles, falling back to index=off,nfs_export=off. overlayfs: "xino" feature enabled using 1 upper inode bits. overlayfs: upperdir is in-use as upperdir/workdir of another mount, mount with '-o index=off' to override exclusive upperdir protection. overlayfs: fs on './bus' does not support file handles, falling back to index=off,nfs_export=off. overlayfs: "xino" feature enabled using 1 upper inode bits. overlayfs: upperdir is in-use as upperdir/workdir of another mount, mount with '-o index=off' to override exclusive upperdir protection. netlink: 32 bytes leftover after parsing attributes in process `syz-executor.0'. overlayfs: conflicting lowerdir path overlayfs: conflicting lowerdir path overlayfs: fs on './bus' does not support file handles, falling back to index=off,nfs_export=off. overlayfs: "xino" feature enabled using 1 upper inode bits. overlayfs: upperdir is in-use as upperdir/workdir of another mount, mount with '-o index=off' to override exclusive upperdir protection. overlayfs: fs on './bus' does not support file handles, falling back to index=off,nfs_export=off. overlayfs: "xino" feature enabled using 1 upper inode bits. overlayfs: upperdir is in-use as upperdir/workdir of another mount, mount with '-o index=off' to override exclusive upperdir protection. overlayfs: unrecognized mount option "uppebLir=./file1" or missing value overlayfs: unrecognized mount option "uppebLir=./file1" or missing value overlayfs: fs on './bus' does not support file handles, falling back to index=off,nfs_export=off. overlayfs: "xino" feature enabled using 1 upper inode bits. overlayfs: upperdir is in-use as upperdir/workdir of another mount, mount with '-o index=off' to override exclusive upperdir protection. netlink: 8 bytes leftover after parsing attributes in process `syz-executor.0'. overlayfs: fs on './bus' does not support file handles, falling back to index=off,nfs_export=off. overlayfs: "xino" feature enabled using 1 upper inode bits. netlink: 8 bytes leftover after parsing attributes in process `syz-executor.0'. overlayfs: upperdir is in-use as upperdir/workdir of another mount, mount with '-o index=off' to override exclusive upperdir protection. overlayfs: fs on './bus' does not support file handles, falling back to index=off,nfs_export=off. overlayfs: "xino" feature enabled using 1 upper inode bits. overlayfs: upperdir is in-use as upperdir/workdir of another mount, mount with '-o index=off' to override exclusive upperdir protection. overlayfs: fs on './bus' does not support file handles, falling back to index=off,nfs_export=off. overlayfs: "xino" feature enabled using 1 upper inode bits. overlayfs: fs on './bus' does not support file handles, falling back to index=off,nfs_export=off. overlayfs: "xino" feature enabled using 1 upper inode bits. overlayfs: upperdir is in-use as upperdir/workdir of another mount, accessing files from both mounts will result in undefined behavior. overlayfs: workdir is in-use as upperdir/workdir of another mount, accessing files from both mounts will result in undefined behavior. overlayfs: unrecognized mount option "l|–erdir=./bus" or missing value overlayfs: unrecognized mount option "l|–erdir=./bus" or missing value overlayfs: missing 'workdir' overlayfs: missing 'workdir' overlayfs: fs on './bus' does not support file handles, falling back to index=off,nfs_export=off. overlayfs: "xino" feature enabled using 1 upper inode bits. overlayfs: upperdir is in-use as upperdir/workdir of another mount, mount with '-o index=off' to override exclusive upperdir protection. overlayfs: unrecognized mount option "upperdi’=./file1" or missing value overlayfs: fs on './bus' does not support file handles, falling back to index=off,nfs_export=off. overlayfs: "xino" feature enabled using 1 upper inode bits. overlayfs: upperdir is in-use as upperdir/workdir of another mount, mount with '-o index=off' to override exclusive upperdir protection. overlayfs: unrecognized mount option "appraise" or missing value overlayfs: bad mount option "redirect_dir=./file0" overlayfs: unrecognized mount option "appraise" or missing value overlayfs: bad mount option "redirect_dir=./file0" overlayfs: unrecognized mount option "lowerlir=./bus" or missing value overlayfs: unrecognized mount option "lowerlir=./bus" or missing value overlayfs: at least 2 lowerdir are needed while upperdir nonexistent overlayfs: at least 2 lowerdir are needed while upperdir nonexistent overlayfs: fs on './bus' does not support file handles, falling back to index=off,nfs_export=off. overlayfs: "xino" feature enabled using 1 upper inode bits. overlayfs: upperdir is in-use as upperdir/workdir of another mount, mount with '-o index=off' to override exclusive upperdir protection. overlayfs: unrecognized mount option "xino=on5." or missing value overlayfs: unrecognized mount option "xino=on5." or missing value overlayfs: failed to resolve './file1': -2 overlayfs: failed to resolve './file1': -2 overlayfs: unrecognized mount option "˙˙˙˙˙˙˙˙" or missing value overlayfs: unrecognized mount option "˙˙˙˙˙˙˙˙" or missing value