bisecting fixing commit since e7d2672c66e4d3675570369bf20856296da312c4
building syzkaller on a60cb4cd840ce786236a00480e8bb1025e0c5fef
testing commit e7d2672c66e4d3675570369bf20856296da312c4 with gcc (GCC) 8.1.0
kernel signature: ed48916ebd82b0c9e1983df7c226f51ef2eb1418d7f2692de79596a20ba8446d
run #0: crashed: INFO: task hung in p9_fd_close
run #1: crashed: INFO: task hung in p9_fd_close
run #2: crashed: INFO: task hung in p9_fd_close
run #3: crashed: INFO: task hung in p9_fd_close
run #4: crashed: INFO: task hung in p9_fd_close
run #5: crashed: INFO: task hung in p9_fd_close
run #6: crashed: INFO: task hung in p9_fd_close
run #7: crashed: no output from test machine
run #8: crashed: no output from test machine
run #9: crashed: no output from test machine
testing current HEAD 2d16cf4817bc6944a2adb5bf4db607c8258e87da
testing commit 2d16cf4817bc6944a2adb5bf4db607c8258e87da with gcc (GCC) 8.1.0
kernel signature: ba5eb4aa9ba6beda799f4c018af388cfade3fd4fa72bcc4431f5977ad428f0f1
run #0: crashed: INFO: task hung in p9_fd_close
run #1: crashed: INFO: task hung in p9_fd_close
run #2: crashed: INFO: task hung in p9_fd_close
run #3: crashed: INFO: task hung in p9_fd_close
run #4: crashed: INFO: task hung in p9_fd_close
run #5: crashed: no output from test machine
run #6: crashed: no output from test machine
run #7: crashed: no output from test machine
run #8: crashed: no output from test machine
run #9: crashed: no output from test machine
revisions tested: 2, total time: 34m16.674663894s (build: 17m48.868076073s, test: 15m49.055088652s)
the crash still happens on HEAD
commit msg: Linux 4.19.125
crash: no output from test machine