syzbot has bisected this issue to:
commit 4977caef05aa154f5e45a232fc4f0e1c74a0c739
Author: Zhang Qiang <qiang.zh...@windriver.com>
Date: Tue Jul 7 02:29:47 2020 +0000
kthread: work could not be queued when worker being destroyed
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12c58f57100000
start commit: 89032636 Add linux-next specific files for 20200708
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=11c58f57100000
console output: https://syzkaller.appspot.com/x/log.txt?x=16c58f57100000
kernel config: https://syzkaller.appspot.com/x/.config?x=64a250ebabc6c320
dashboard link: https://syzkaller.appspot.com/bug?extid=fa64e680a1ff32087778
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16bf9f2f100000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=118380ed100000
Reported-by: syzbot+fa64e680a1ff32087...@syzkaller.appspotmail.com
Fixes: 4977caef05aa ("kthread: work could not be queued when worker being
destroyed")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
