INFO: task hung in evdev_release

[syzbot]

Hello,

syzbot found the following crash on:

HEAD commit: b5123fd4 Merge 4.14.115 into android-4.14
git tree: android-4.14
console output: https://syzkaller.appspot.com/x/log.txt?x=14712948a00000
kernel config: https://syzkaller.appspot.com/x/.config?x=2319c8ab80e5b9b8
dashboard link: https://syzkaller.appspot.com/bug?extid=c3601a65dab4c6f3c808
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+c3601a...@syzkaller.appspotmail.com

INFO: task syz-executor.1:3382 blocked for more than 140 seconds.
Not tainted 4.14.115+ #64
[10210] 0 10210 18146 8762 24 3 0
0 syz-executor.4
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[10212] 0 10212 18113 8760 24 3 0
0 syz-executor.4
[10213] 0 10213 18113 8760 24 3 0
0 syz-executor.4
syz-executor.1 D28576 3382 1867 0x80000006
Call Trace:
[10214] 0 10214 18113 8760 24 3 0
0 syz-executor.4
[10215] 0 10215 18113 8760 24 3 0
0 syz-executor.4
[10216] 0 10216 18113 8760 24 3 0
0 syz-executor.4
schedule+0x92/0x1c0 kernel/sched/core.c:3498
schedule_timeout+0x736/0xe80 kernel/time/timer.c:1721
[10217] 0 10217 18113 8760 24 3 0
0 syz-executor.4
[10218] 0 10218 18113 8760 24 3 0
0 syz-executor.4
[10219] 0 10219 18113 8760 24 3 0
0 syz-executor.4
[10221] 0 10221 18113 8760 24 3 0
0 syz-executor.4
do_wait_for_common kernel/sched/completion.c:91 [inline]
__wait_for_common kernel/sched/completion.c:112 [inline]
wait_for_common+0x29c/0x470 kernel/sched/completion.c:123
__wait_rcu_gp+0x235/0x2f0 kernel/rcu/update.c:413
[10222] 0 10222 18113 8760 24 3 0
0 syz-executor.4
[10224] 0 10224 18113 8760 24 3 0
0 syz-executor.4
[10225] 0 10225 18146 8762 24 3 0
0 syz-executor.4
synchronize_rcu.part.0+0xc1/0xd0 kernel/rcu/tree_plugin.h:764
[10226] 0 10226 18113 8760 24 3 0
0 syz-executor.4
[10228] 0 10228 18113 8760 24 3 0
0 syz-executor.4
[10229] 0 10229 18113 8760 24 3 0
0 syz-executor.4
evdev_release+0xa2/0x1a0 drivers/input/evdev.c:475
__fput+0x25e/0x700 fs/file_table.c:210
task_work_run+0x118/0x190 kernel/task_work.c:113
exit_task_work include/linux/task_work.h:22 [inline]
do_exit+0x903/0x2960 kernel/exit.c:874
[10230] 0 10230 18113 8760 24 3 0
0 syz-executor.4
[10231] 0 10231 18113 8760 24 3 0
0 syz-executor.4
[10232] 0 10232 18113 8760 24 3 0
0 syz-executor.4
[10233] 0 10233 18113 8760 24 3 0
0 syz-executor.4
[10235] 0 10235 18113 8760 24 3 0
0 syz-executor.4
[10236] 0 10236 18113 8760 24 3 0
0 syz-executor.4
[10237] 0 10237 18113 8760 24 3 0
0 syz-executor.4
[10238] 0 10238 18146 8762 24 3 0
0 syz-executor.4
[10239] 0 10239 18113 8760 24 3 0
0 syz-executor.4
[10240] 0 10240 18113 8760 24 3 0
0 syz-executor.4
[10241] 0 10241 18146 8762 24 3 0
0 syz-executor.4
[10242] 0 10242 18113 8760 24 3 0
0 syz-executor.4
INFO: task kworker/1:0:14722 blocked for more than 140 seconds.
[10243] 0 10243 18113 8760 24 3 0
0 syz-executor.4
[10244] 0 10244 18113 8760 24 3 0
0 syz-executor.4
Not tainted 4.14.115+ #64
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
kworker/1:0 D27736 14722 2 0x80000000
Workqueue: events xfrm_state_gc_task
[10245] 0 10245 18113 8760 24 3 0
0 syz-executor.4
Call Trace:
[10246] 0 10246 18146 8762 24 3 0
0 syz-executor.4
schedule+0x92/0x1c0 kernel/sched/core.c:3498
[10247] 0 10247 18113 8760 24 3 0
0 syz-executor.4
[10248] 0 10248 18113 8760 24 3 0
0 syz-executor.4
[10249] 0 10249 18113 8760 24 3 0
0 syz-executor.4
schedule_timeout+0x736/0xe80 kernel/time/timer.c:1721
do_wait_for_common kernel/sched/completion.c:91 [inline]
__wait_for_common kernel/sched/completion.c:112 [inline]
wait_for_common+0x29c/0x470 kernel/sched/completion.c:123
[10250] 0 10250 18113 8760 24 3 0
0 syz-executor.4
[10251] 0 10251 18113 8760 24 3 0
0 syz-executor.4


---
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 syzk...@googlegroups.com.

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

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.