syzbot <syzbot+e1628a5e87492e6f1b76@xxxxxxxxxxxxxxxxxxxxxxxxx> writes: > syzbot has bisected this bug to: > > commit abd5f00844ec7fa507064ee4a22b3605c64c7d31 > Author: Kalle Valo <kvalo@xxxxxxxxxxxxxx> > Date: Tue Mar 27 07:06:18 2018 +0000 > > Merge ath-next from > git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git > > bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12f9389b200000 > start commit: 4aa9fc2a Revert "mm, memory_hotplug: initialize struct pag.. > git tree: upstream > final crash: https://syzkaller.appspot.com/x/report.txt?x=11f9389b200000 > console output: https://syzkaller.appspot.com/x/log.txt?x=16f9389b200000 > kernel config: https://syzkaller.appspot.com/x/.config?x=4fceea9e2d99ac20 > dashboard link: https://syzkaller.appspot.com/bug?extid=e1628a5e87492e6f1b76 > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=175c96ef400000 > > Reported-by: syzbot+e1628a5e87492e6f1b76@xxxxxxxxxxxxxxxxxxxxxxxxx > Fixes: abd5f00844ec ("Merge ath-next from > git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git") > > For information about bisection process see: https://goo.gl/tpsmEJ#bisection I highly doubt about the bisection result pointing to this merge. My ath.git tree only touches drivers/net/wireless/ath and I can't see how the drivers could cause the reported deadlock. I don't even see any of the ath drivers loaded. -- Kalle Valo
