====================================================== WARNING: possible circular locking dependency detected 5.6.0-rc3-next-20200225-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor106/9725 is trying to acquire lock: ffff88809747d2a0 (&tty->termios_rwsem){++++}, at: n_tty_receive_buf_common+0x8a/0x2b70 drivers/tty/n_tty.c:1705 but task is already holding lock: ffffffff8a141ca0 (sel_lock){+.+.}, at: paste_selection+0x15a/0x4d0 drivers/tty/vt/selection.c:379 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (sel_lock){+.+.}: __mutex_lock_common kernel/locking/mutex.c:956 [inline] __mutex_lock+0x156/0x13c0 kernel/locking/mutex.c:1103 mutex_lock_nested+0x16/0x20 kernel/locking/mutex.c:1118 set_selection_kernel+0x39d/0x13d0 drivers/tty/vt/selection.c:222 set_selection_user+0x95/0xd9 drivers/tty/vt/selection.c:186 tioclinux+0x11c/0x480 drivers/tty/vt/vt.c:3051 vt_ioctl+0x1a53/0x26a0 drivers/tty/vt/vt_ioctl.c:379 tty_ioctl+0xa37/0x14f0 drivers/tty/tty_io.c:2660 vfs_ioctl fs/ioctl.c:47 [inline] ksys_ioctl+0x123/0x180 fs/ioctl.c:763 __do_sys_ioctl fs/ioctl.c:772 [inline] __se_sys_ioctl fs/ioctl.c:770 [inline] __x64_sys_ioctl+0x73/0xb0 fs/ioctl.c:770 do_syscall_64+0xfa/0x790 arch/x86/entry/common.c:295 entry_SYSCALL_64_after_hwframe+0x49/0xbe -> #1 (console_lock){+.+.}: console_lock+0x47/0x80 kernel/printk/printk.c:2290 con_flush_chars drivers/tty/vt/vt.c:3224 [inline] con_flush_chars+0x3d/0xa0 drivers/tty/vt/vt.c:3216 n_tty_write+0xc85/0x1080 drivers/tty/n_tty.c:2350 do_tty_write drivers/tty/tty_io.c:962 [inline] tty_write+0x496/0x7f0 drivers/tty/tty_io.c:1046 __vfs_write+0x8a/0x110 fs/read_write.c:494 vfs_write+0x268/0x5d0 fs/read_write.c:558 ksys_write+0x14f/0x290 fs/read_write.c:611 __do_sys_write fs/read_write.c:623 [inline] __se_sys_write fs/read_write.c:620 [inline] __x64_sys_write+0x73/0xb0 fs/read_write.c:620 do_syscall_64+0xfa/0x790 arch/x86/entry/common.c:295 entry_SYSCALL_64_after_hwframe+0x49/0xbe -> #0 (&tty->termios_rwsem){++++}: check_prev_add kernel/locking/lockdep.c:2481 [inline] check_prevs_add kernel/locking/lockdep.c:2586 [inline] validate_chain kernel/locking/lockdep.c:3203 [inline] __lock_acquire+0x29cd/0x6320 kernel/locking/lockdep.c:4190 lock_acquire+0x190/0x410 kernel/locking/lockdep.c:4720 down_read+0x95/0x440 kernel/locking/rwsem.c:1492 n_tty_receive_buf_common+0x8a/0x2b70 drivers/tty/n_tty.c:1705 n_tty_receive_buf2+0x34/0x40 drivers/tty/n_tty.c:1777 tty_ldisc_receive_buf+0xad/0x1c0 drivers/tty/tty_buffer.c:461 paste_selection+0x1ff/0x4d0 drivers/tty/vt/selection.c:394 tioclinux+0x133/0x480 drivers/tty/vt/vt.c:3056 vt_ioctl+0x1a53/0x26a0 drivers/tty/vt/vt_ioctl.c:379 tty_ioctl+0xa37/0x14f0 drivers/tty/tty_io.c:2660 vfs_ioctl fs/ioctl.c:47 [inline] ksys_ioctl+0x123/0x180 fs/ioctl.c:763 __do_sys_ioctl fs/ioctl.c:772 [inline] __se_sys_ioctl fs/ioctl.c:770 [inline] __x64_sys_ioctl+0x73/0xb0 fs/ioctl.c:770 do_syscall_64+0xfa/0x790 arch/x86/entry/common.c:295 entry_SYSCALL_64_after_hwframe+0x49/0xbe other info that might help us debug this: Chain exists of: &tty->termios_rwsem --> console_lock --> sel_lock Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(sel_lock); lock(console_lock); lock(sel_lock); lock(&tty->termios_rwsem); *** DEADLOCK *** 3 locks held by syz-executor106/9725: #0: ffff88809747d090 (&tty->ldisc_sem){++++}, at: ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:340 #1: ffff8880a82f00a8 (&buf->lock){+.+.}, at: tty_buffer_lock_exclusive+0x30/0x40 drivers/tty/tty_buffer.c:61 #2: ffffffff8a141ca0 (sel_lock){+.+.}, at: paste_selection+0x15a/0x4d0 drivers/tty/vt/selection.c:379 stack backtrace: CPU: 0 PID: 9725 Comm: syz-executor106 Not tainted 5.6.0-rc3-next-20200225-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+0x197/0x210 lib/dump_stack.c:118 print_circular_bug.isra.0.cold+0x163/0x172 kernel/locking/lockdep.c:1688 check_noncircular+0x32e/0x3e0 kernel/locking/lockdep.c:1812 check_prev_add kernel/locking/lockdep.c:2481 [inline] check_prevs_add kernel/locking/lockdep.c:2586 [inline] validate_chain kernel/locking/lockdep.c:3203 [inline] __lock_acquire+0x29cd/0x6320 kernel/locking/lockdep.c:4190 lock_acquire+0x190/0x410 kernel/locking/lockdep.c:4720 down_read+0x95/0x440 kernel/locking/rwsem.c:1492 n_tty_receive_buf_common+0x8a/0x2b70 drivers/tty/n_tty.c:1705 n_tty_receive_buf2+0x34/0x40 drivers/tty/n_tty.c:1777 tty_ldisc_receive_buf+0xad/0x1c0 drivers/tty/tty_buffer.c:461 paste_selection+0x1ff/0x4d0 drivers/tty/vt/selection.c:394 tioclinux+0x133/0x480 drivers/tty/vt/vt.c:3056 vt_ioctl+0x1a53/0x26a0 drivers/tty/vt/vt_ioctl.c:379 tty_ioctl+0xa37/0x14f0 drivers/tty/tty_io.c:2660 vfs_ioctl fs/ioctl.c:47 [inline] ksys_ioctl+0x123/0x180 fs/ioctl.c:763 __do_sys_ioctl fs/ioctl.c:772 [inline] __se_sys_ioctl fs/ioctl.c:770 [inline] __x64_sys_ioctl+0x73/0xb0 fs/ioctl.c:770 do_syscall_64+0xfa/0x790 arch/x86/entry/common.c:295 entry_SYSCALL_64_after_hwframe+0x49/0xbe RIP: 0033:0x440269 Code: 18 89 d0 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 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 0f 83 5b 14 fc ff c3 66 2e 0f 1f 84 00 00 00 00