syzbot


INFO: task hung in ucma_destroy_id

Status: fixed on 2018/07/05 05:52
Reported-by: syzbot+449737930e1faf08523e@syzkaller.appspotmail.com
Fix commit: ef95a90ae6f4 RDMA/ucma: ucma_context reference leak in error path
First crash: 1731d, last: 1693d

Sample crash report:
INFO: task syzkaller681645:4295 blocked for more than 120 seconds.
      Not tainted 4.16.0-rc7+ #3
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syzkaller681645 D20744  4295   4293 0x00000000
Call Trace:
 context_switch kernel/sched/core.c:2862 [inline]
 __schedule+0x8fb/0x1ec0 kernel/sched/core.c:3440
 schedule+0xf5/0x430 kernel/sched/core.c:3499
 schedule_timeout+0x1a3/0x230 kernel/time/timer.c:1777
 do_wait_for_common kernel/sched/completion.c:86 [inline]
 __wait_for_common kernel/sched/completion.c:107 [inline]
 wait_for_common kernel/sched/completion.c:118 [inline]
 wait_for_completion+0x415/0x770 kernel/sched/completion.c:139
 ucma_destroy_id+0x2f0/0x500 drivers/infiniband/core/ucma.c:611
 ucma_write+0x2d6/0x3d0 drivers/infiniband/core/ucma.c:1649
 __vfs_write+0xef/0x970 fs/read_write.c:480
 vfs_write+0x189/0x510 fs/read_write.c:544
 SYSC_write fs/read_write.c:589 [inline]
 SyS_write+0xef/0x220 fs/read_write.c:581
 do_syscall_64+0x281/0x940 arch/x86/entry/common.c:287
 entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x440719
RSP: 002b:00007ffc7e451f28 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007ffc7e451f50 RCX: 0000000000440719
RDX: 0000000000000018 RSI: 0000000020000080 RDI: 0000000000000003
RBP: 0000000000000000 R08: 00007ffc7e451fa0 R09: 00007ffc7e451fa0
R10: 00007ffc7e451fa0 R11: 0000000000000246 R12: 0000000000402040
R13: 00000000004020d0 R14: 0000000000000000 R15: 0000000000000000

Showing all locks held in the system:
2 locks held by khungtaskd/868:
 #0:  (rcu_read_lock){....}, at: [<00000000dbcbeec6>] check_hung_uninterruptible_tasks kernel/hung_task.c:175 [inline]
 #0:  (rcu_read_lock){....}, at: [<00000000dbcbeec6>] watchdog+0x1c5/0xd60 kernel/hung_task.c:249
 #1:  (tasklist_lock){.+.+}, at: [<000000003f35a062>] debug_show_all_locks+0xd3/0x3d0 kernel/locking/lockdep.c:4470
1 lock held by rsyslogd/4176:
 #0:  (&f->f_pos_lock){+.+.}, at: [<00000000337d089e>] __fdget_pos+0x12b/0x190 fs/file.c:765
2 locks held by getty/4266:
 #0:  (&tty->ldisc_sem){++++}, at: [<0000000091eb7f81>] ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:365
 #1:  (&ldata->atomic_read_lock){+.+.}, at: [<00000000c6c6bab6>] n_tty_read+0x2ef/0x1a40 drivers/tty/n_tty.c:2131
2 locks held by getty/4267:
 #0:  (&tty->ldisc_sem){++++}, at: [<0000000091eb7f81>] ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:365
 #1:  (&ldata->atomic_read_lock){+.+.}, at: [<00000000c6c6bab6>] n_tty_read+0x2ef/0x1a40 drivers/tty/n_tty.c:2131
2 locks held by getty/4268:
 #0:  (&tty->ldisc_sem){++++}, at: [<0000000091eb7f81>] ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:365
 #1:  (&ldata->atomic_read_lock){+.+.}, at: [<00000000c6c6bab6>] n_tty_read+0x2ef/0x1a40 drivers/tty/n_tty.c:2131
2 locks held by getty/4269:
 #0:  (&tty->ldisc_sem){++++}, at: [<0000000091eb7f81>] ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:365
 #1:  (&ldata->atomic_read_lock){+.+.}, at: [<00000000c6c6bab6>] n_tty_read+0x2ef/0x1a40 drivers/tty/n_tty.c:2131
2 locks held by getty/4270:
 #0:  (&tty->ldisc_sem){++++}, at: [<0000000091eb7f81>] ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:365
 #1:  (&ldata->atomic_read_lock){+.+.}, at: [<00000000c6c6bab6>] n_tty_read+0x2ef/0x1a40 drivers/tty/n_tty.c:2131
2 locks held by getty/4271:
 #0:  (&tty->ldisc_sem){++++}, at: [<0000000091eb7f81>] ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:365
 #1:  (&ldata->atomic_read_lock){+.+.}, at: [<00000000c6c6bab6>] n_tty_read+0x2ef/0x1a40 drivers/tty/n_tty.c:2131
2 locks held by getty/4272:
 #0:  (&tty->ldisc_sem){++++}, at: [<0000000091eb7f81>] ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:365
 #1:  (&ldata->atomic_read_lock){+.+.}, at: [<00000000c6c6bab6>] n_tty_read+0x2ef/0x1a40 drivers/tty/n_tty.c:2131

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

NMI backtrace for cpu 0
CPU: 0 PID: 868 Comm: khungtaskd Not tainted 4.16.0-rc7+ #3
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+0x194/0x24d lib/dump_stack.c:53
 nmi_cpu_backtrace+0x1d2/0x210 lib/nmi_backtrace.c:103
 nmi_trigger_cpumask_backtrace+0x123/0x180 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:138 [inline]
 check_hung_task kernel/hung_task.c:132 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:190 [inline]
 watchdog+0x90c/0xd60 kernel/hung_task.c:249
 kthread+0x33c/0x400 kernel/kthread.c:238
 ret_from_fork+0x3a/0x50 arch/x86/entry/entry_64.S:406
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1 skipped: idling at native_safe_halt+0x6/0x10 arch/x86/include/asm/irqflags.h:54

Crashes (46):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Title
ci-upstream-kasan-gce-root 2018/03/28 09:55 upstream 3eb2ce825ea1 bf5e585c .config log report syz C
ci-upstream-kasan-gce-root 2018/04/18 22:08 upstream a27fc14219f2 829f0234 .config log report
ci-upstream-kasan-gce 2018/04/12 06:53 upstream b284d4d5a678 9cd56d71 .config log report
ci-upstream-kasan-gce-root 2018/04/01 22:05 upstream 10b84daddbec dc889257 .config log report
ci-upstream-kasan-gce-root 2018/03/28 23:59 upstream 3eb2ce825ea1 bf5e585c .config log report
ci-upstream-kasan-gce 2018/03/27 22:04 upstream 3eb2ce825ea1 bf5e585c .config log report
ci-upstream-kasan-gce-root 2018/03/26 23:53 upstream 3eb2ce825ea1 0ca7878b .config log report
ci-upstream-kasan-gce 2018/03/26 12:18 upstream 3eb2ce825ea1 e033c1f1 .config log report
ci-upstream-kasan-gce-root 2018/03/25 23:44 upstream bcfc1f455466 e033c1f1 .config log report
ci-upstream-kasan-gce 2018/03/25 14:16 upstream bcfc1f455466 e033c1f1 .config log report
ci-upstream-kasan-gce 2018/03/24 08:48 upstream 99fec39e7725 2e9d9054 .config log report
ci-upstream-kasan-gce 2018/03/23 17:49 upstream f36b7534b833 2e9d9054 .config log report
ci-upstream-kasan-gce 2018/03/23 02:12 upstream c4f4d2f91772 2e9d9054 .config log report
ci-upstream-kasan-gce 2018/03/22 05:17 upstream 3215b9d57a2c 95c88d7a .config log report
ci-upstream-kasan-gce 2018/03/22 04:33 upstream 3215b9d57a2c 95c88d7a .config log report
ci-upstream-kasan-gce 2018/03/22 03:11 upstream 3215b9d57a2c 95c88d7a .config log report
ci-upstream-kasan-gce 2018/03/21 14:39 upstream 3215b9d57a2c f63eeee9 .config log report
ci-upstream-kasan-gce 2018/03/21 14:23 upstream 3215b9d57a2c f63eeee9 .config log report
ci-upstream-kasan-gce 2018/03/21 13:18 upstream 3215b9d57a2c f63eeee9 .config log report
ci-upstream-kasan-gce 2018/03/21 08:38 upstream 3215b9d57a2c 113a43ff .config log report
ci-upstream-kasan-gce 2018/03/21 00:40 upstream 1b5f3ba415fe 113a43ff .config log report
ci-upstream-kasan-gce 2018/03/20 16:20 upstream 1b5f3ba415fe 72c33b66 .config log report
ci-upstream-kasan-gce 2018/03/19 15:25 upstream c698ca527893 7e7d7ed2 .config log report
ci-upstream-kasan-gce 2018/03/19 00:57 upstream 9e1909b9da04 08dacaa0 .config log report
ci-upstream-kasan-gce 2018/03/18 22:33 upstream 9e1909b9da04 08dacaa0 .config log report
ci-upstream-kasan-gce 2018/03/18 11:28 upstream 8f5fd927c3a7 08dacaa0 .config log report
ci-upstream-kasan-gce 2018/03/17 17:28 upstream 8f5fd927c3a7 08dacaa0 .config log report
ci-upstream-kasan-gce 2018/03/16 14:03 upstream df09348f78dc 08dacaa0 .config log report
ci-upstream-kasan-gce 2018/03/14 03:27 upstream fc6eabbbf8ef 08dacaa0 .config log report
ci-upstream-kasan-gce 2018/03/13 03:41 upstream fc6eabbbf8ef f505ca4b .config log report
ci-upstream-kasan-gce 2018/03/12 04:20 upstream abeb75218aeb 36d1c454 .config log report
ci-upstream-kasan-gce-386 2018/04/05 05:14 upstream f2d285669aae 676bd07e .config log report
ci-upstream-kasan-gce-386 2018/03/29 17:19 upstream 0b412605ef5f d47f0ed6 .config log report
ci-upstream-kasan-gce-386 2018/03/29 02:02 upstream a2601d78b77a bf5e585c .config log report
ci-upstream-kasan-gce-386 2018/03/29 00:19 upstream 3eb2ce825ea1 bf5e585c .config log report
ci-upstream-kasan-gce-386 2018/03/28 08:22 upstream 3eb2ce825ea1 bf5e585c .config log report
ci-upstream-kasan-gce-386 2018/03/26 14:37 upstream 3eb2ce825ea1 e033c1f1 .config log report
ci-upstream-kasan-gce-386 2018/03/26 07:24 upstream cb6416592bc2 e033c1f1 .config log report
ci-upstream-kasan-gce-386 2018/03/23 23:24 upstream f36b7534b833 2e9d9054 .config log report
ci-upstream-kasan-gce-386 2018/03/21 06:47 upstream 3215b9d57a2c 113a43ff .config log report
ci-upstream-kasan-gce-386 2018/03/21 04:31 upstream 3215b9d57a2c 113a43ff .config log report
ci-upstream-kasan-gce-386 2018/03/19 14:18 upstream c698ca527893 7e7d7ed2 .config log report
ci-upstream-kasan-gce-386 2018/03/17 19:35 upstream 8f5fd927c3a7 08dacaa0 .config log report
ci-upstream-kasan-gce-386 2018/03/15 17:30 upstream 0aa3fdb8b3a6 08dacaa0 .config log report
ci-upstream-kasan-gce-386 2018/03/12 08:37 upstream abeb75218aeb 36d1c454 .config log report
ci-upstream-kasan-gce-386 2018/03/11 12:20 upstream 3266b5bd97ea 36d1c454 .config log report
* Struck through repros no longer work on HEAD.