INFO: task hung in vt_resize

From: syzbot
Date: Mon Mar 02 2020 - 00:16:13 EST

Next message: Ravi Bangoria: "[RFC 00/11] perf: Enhancing perf to export processor hazard information"
Previous message: syzbot: "KASAN: use-after-free Write in hci_sock_bind (2)"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hello,

syzbot found the following crash on:

HEAD commit: f8788d86 Linux 5.6-rc3
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=157758f9e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=9833e26bab355358
dashboard link: https://syzkaller.appspot.com/bug?extid=7dd2cfed71fe7276d543
compiler: gcc (GCC) 9.0.0 20181231 (experimental)

Unfortunately, I don't have any reproducer for this crash yet.

IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+7dd2cfed71fe7276d543@xxxxxxxxxxxxxxxxxxxxxxxxx

INFO: task syz-executor.3:19080 blocked for more than 143 seconds.
Not tainted 5.6.0-rc3-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor.3 D28376 19080 9706 0x00000004
Call Trace:
context_switch kernel/sched/core.c:3380 [inline]
__schedule+0x934/0x1f90 kernel/sched/core.c:4080
schedule+0xdc/0x2b0 kernel/sched/core.c:4154
schedule_timeout+0x717/0xc50 kernel/time/timer.c:1871
__down_common kernel/locking/semaphore.c:220 [inline]
__down+0x176/0x2c0 kernel/locking/semaphore.c:237
down+0x64/0x90 kernel/locking/semaphore.c:61
console_lock+0x29/0x80 kernel/printk/printk.c:2289
vt_resize+0x48/0xf0 drivers/tty/vt/vt.c:1335
tiocswinsz drivers/tty/tty_io.c:2281 [inline]
tty_ioctl+0x78a/0x14f0 drivers/tty/tty_io.c:2580
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:294
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x45c449
Code: ad b6 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 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 7b b6 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f274a6bbc78 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f274a6bc6d4 RCX: 000000000045c449
RDX: 0000000020000200 RSI: 0000000000005414 RDI: 0000000000000003
RBP: 000000000076bfc0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000ffffffff
R13: 000000000000058d R14: 00000000004c7e1b R15: 000000000076bfcc
INFO: task syz-executor.1:19126 blocked for more than 143 seconds.
Not tainted 5.6.0-rc3-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor.1 D26248 19126 9695 0x00004004
Call Trace:
context_switch kernel/sched/core.c:3380 [inline]
__schedule+0x934/0x1f90 kernel/sched/core.c:4080
schedule+0xdc/0x2b0 kernel/sched/core.c:4154
schedule_timeout+0x717/0xc50 kernel/time/timer.c:1871
__down_common kernel/locking/semaphore.c:220 [inline]
__down+0x176/0x2c0 kernel/locking/semaphore.c:237
down+0x64/0x90 kernel/locking/semaphore.c:61
console_lock+0x29/0x80 kernel/printk/printk.c:2289
vcs_open+0x67/0xd0 drivers/tty/vt/vc_screen.c:688
chrdev_open+0x245/0x6b0 fs/char_dev.c:414
do_dentry_open+0x4e6/0x1380 fs/open.c:797
vfs_open+0xa0/0xd0 fs/open.c:914
do_last fs/namei.c:3490 [inline]
path_openat+0x12ee/0x3490 fs/namei.c:3607
do_filp_open+0x192/0x260 fs/namei.c:3637
do_sys_openat2+0x5eb/0x7e0 fs/open.c:1149
do_sys_open+0xf2/0x180 fs/open.c:1165
__do_sys_openat fs/open.c:1179 [inline]
__se_sys_openat fs/open.c:1174 [inline]
__x64_sys_openat+0x9d/0x100 fs/open.c:1174
do_syscall_64+0xfa/0x790 arch/x86/entry/common.c:294
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x45c449
Code: ad b6 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 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 7b b6 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f108721cc78 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007f108721d6d4 RCX: 000000000045c449
RDX: 0000000000000200 RSI: 00000000200001c0 RDI: ffffffffffffff9c
RBP: 000000000076bf20 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000ffffffff
R13: 00000000000007ff R14: 00000000004ca787 R15: 000000000076bf2c

Showing all locks held in the system:
4 locks held by kworker/u4:7/667:
1 lock held by khungtaskd/1132:
#0: ffffffff89bac280 (rcu_read_lock){....}, at: debug_show_all_locks+0x5f/0x279 kernel/locking/lockdep.c:5333
1 lock held by rsyslogd/9561:
#0: ffff888098823160 (&f->f_pos_lock){+.+.}, at: __fdget_pos+0xee/0x110 fs/file.c:821
2 locks held by getty/9651:
#0: ffff8880a7141090 (&tty->ldisc_sem){++++}, at: ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:340
#1: ffffc900059232e0 (&ldata->atomic_read_lock){+.+.}, at: n_tty_read+0x220/0x1bf0 drivers/tty/n_tty.c:2156
2 locks held by getty/9652:
#0: ffff88809f514090 (&tty->ldisc_sem){++++}, at: ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:340
#1: ffffc900059cb2e0 (&ldata->atomic_read_lock){+.+.}, at: n_tty_read+0x220/0x1bf0 drivers/tty/n_tty.c:2156
2 locks held by getty/9653:
#0: ffff88809aae1090 (&tty->ldisc_sem){++++}, at: ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:340
#1: ffffc900059db2e0 (&ldata->atomic_read_lock){+.+.}, at: n_tty_read+0x220/0x1bf0 drivers/tty/n_tty.c:2156
2 locks held by getty/9654:
#0: ffff88809fc70090 (&tty->ldisc_sem){++++}, at: ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:340
#1: ffffc9000592b2e0 (&ldata->atomic_read_lock){+.+.}, at: n_tty_read+0x220/0x1bf0 drivers/tty/n_tty.c:2156
2 locks held by getty/9655:
#0: ffff88809f51a090 (&tty->ldisc_sem){++++}, at: ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:340
#1: ffffc900059bb2e0 (&ldata->atomic_read_lock){+.+.}, at: n_tty_read+0x220/0x1bf0 drivers/tty/n_tty.c:2156
2 locks held by getty/9656:
#0: ffff888090d01090 (&tty->ldisc_sem){++++}, at: ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:340
#1: ffffc900059ab2e0 (&ldata->atomic_read_lock){+.+.}, at: n_tty_read+0x220/0x1bf0 drivers/tty/n_tty.c:2156
2 locks held by getty/9657:
#0: ffff8880a79c2090 (&tty->ldisc_sem){++++}, at: ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:340
#1: ffffc900059032e0 (&ldata->atomic_read_lock){+.+.}, at: n_tty_read+0x220/0x1bf0 drivers/tty/n_tty.c:2156
1 lock held by syz-executor.3/19078:

=============================================

NMI backtrace for cpu 1
CPU: 1 PID: 1132 Comm: khungtaskd Not tainted 5.6.0-rc3-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
nmi_cpu_backtrace.cold+0x70/0xb2 lib/nmi_backtrace.c:101
nmi_trigger_cpumask_backtrace+0x23b/0x28b lib/nmi_backtrace.c:62
arch_trigger_cpumask_backtrace+0x14/0x20 arch/x86/kernel/apic/hw_nmi.c:38
trigger_all_cpu_backtrace include/linux/nmi.h:146 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:205 [inline]
watchdog+0xb11/0x10c0 kernel/hung_task.c:289
kthread+0x361/0x430 kernel/kthread.c:255
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:352
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 19078 Comm: syz-executor.3 Not tainted 5.6.0-rc3-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:__sanitizer_cov_trace_pc+0x3b/0x50 kernel/kcov.c:192
Code: 97 8c 7e 81 e2 00 01 1f 00 48 8b 75 08 75 2b 8b 90 80 13 00 00 83 fa 02 75 20 48 8b 88 88 13 00 00 8b 80 84 13 00 00 48 8b 11 <48> 83 c2 01 48 39 d0 76 07 48 89 34 d1 48 89 11 5d c3 0f 1f 00 65
RSP: 0018:ffffc90007567680 EFLAGS: 00000246
RAX: 0000000000040000 RBX: 0000000000000000 RCX: ffffc900101b6000
RDX: 000000000003ffff RSI: ffffffff83c82685 RDI: ffff8880a3de1000
RBP: ffffc90007567680 R08: 0000000000001400 R09: 0000000000000040
R10: ffffed10147bc5d3 R11: ffff8880a3de2e9f R12: 0000000000001400
R13: 0000000000000040 R14: ffff8880000a0000 R15: 0000000000000000
FS: 00007f274a6dd700(0000) GS:ffff8880ae800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffff600400 CR3: 000000004081a000 CR4: 00000000001426f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
bitfill_aligned+0x25/0x210 drivers/video/fbdev/core/cfbfillrect.c:40
cfb_fillrect+0x423/0x7c0 drivers/video/fbdev/core/cfbfillrect.c:327
vga16fb_fillrect+0x6ce/0x19b0 drivers/video/fbdev/vga16fb.c:951
bit_clear_margins+0x30b/0x530 drivers/video/fbdev/core/bitblit.c:232
fbcon_clear_margins+0x1e9/0x250 drivers/video/fbdev/core/fbcon.c:1379
fbcon_switch+0xd7f/0x17f0 drivers/video/fbdev/core/fbcon.c:2361
redraw_screen+0x2b6/0x7d0 drivers/tty/vt/vt.c:1008
vc_do_resize+0x10c9/0x1460 drivers/tty/vt/vt.c:1295
vt_resize+0xaa/0xf0 drivers/tty/vt/vt.c:1336
tiocswinsz drivers/tty/tty_io.c:2281 [inline]
tty_ioctl+0x78a/0x14f0 drivers/tty/tty_io.c:2580
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:294
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x45c449
Code: ad b6 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 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 7b b6 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f274a6dcc78 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f274a6dd6d4 RCX: 000000000045c449
RDX: 0000000020000200 RSI: 0000000000005414 RDI: 0000000000000003
RBP: 000000000076bf20 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000ffffffff
R13: 000000000000058d R14: 00000000004c7e1b R15: 000000000076bf2c

---
This bug is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@xxxxxxxxxxxxxxxxx

syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

Next message: Ravi Bangoria: "[RFC 00/11] perf: Enhancing perf to export processor hazard information"
Previous message: syzbot: "KASAN: use-after-free Write in hci_sock_bind (2)"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]