On 3/30/19 2:58 PM, syzbot wrote:
syzbot has bisected this bug to:
commit 669de8bda87b92ab9a2fc663b3f5743c2ad1ae9f
Author: Bart Van Assche <bvanassche@xxxxxxx>
Date: Thu Feb 14 23:00:54 2019 +0000
kernel/workqueue: Use dynamic lockdep keys for workqueues
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17f1bacd200000
start commit: 0e40da3e Merge tag 'kbuild-fixes-v5.1' of
git://git.kernel..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=1409bacd200000
console output: https://syzkaller.appspot.com/x/log.txt?x=1009bacd200000
kernel config: https://syzkaller.appspot.com/x/.config?x=8dcdce25ea72bedf
dashboard link:
https://syzkaller.appspot.com/bug?extid=6f39a9deb697359fe520
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10e1bacd200000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1120fe0f200000
Reported-by: syzbot+6f39a9deb697359fe520@xxxxxxxxxxxxxxxxxxxxxxxxx
Fixes: 669de8bda87b ("kernel/workqueue: Use dynamic lockdep keys for
workqueues")
For information about bisection process see:
https://goo.gl/tpsmEJ#bisection
Hi Dmitry,
This bisection result doesn't make sense to me. As one can see, the
message "BUG: MAX_STACK_TRACE_ENTRIES too low!" does not occur in the
console output the above console output URL points at.
Bart.
