On Fri, Mar 22, 2019 at 8:08 AM syzbot <syzbot+06283a66a648cd073885@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote: > > syzbot has bisected this bug to: > > commit 4493b81bea24269df898339dee638d7c5cb2b2df > Author: Mahesh Bandewar <maheshb@xxxxxxxxxx> > Date: Wed Mar 8 18:55:54 2017 +0000 > > bonding: initialize work-queues during creation of bond +linux-can I think I will disable CONFIG_CAN before v4.12. It causes too many false results for v4.12..v4.11 range. It always leads to a wrong decision for first 3 steps, then no chances of correct bisection anymore. > bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=176d1617200000 > start commit: 4493b81b bonding: initialize work-queues during creation o.. > git tree: upstream > final crash: https://syzkaller.appspot.com/x/report.txt?x=14ed1617200000 > console output: https://syzkaller.appspot.com/x/log.txt?x=10ed1617200000 > kernel config: https://syzkaller.appspot.com/x/.config?x=62118286bb772a24 > dashboard link: https://syzkaller.appspot.com/bug?extid=06283a66a648cd073885 > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15701a33400000 > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=154c8e4d400000 > > Reported-by: syzbot+06283a66a648cd073885@xxxxxxxxxxxxxxxxxxxxxxxxx > Fixes: 4493b81bea24 ("bonding: initialize work-queues during creation of > bond") > > For information about bisection process see: https://goo.gl/tpsmEJ#bisection
