Re: possible deadlock in lock_trace (3)

syzbot suspects this bug was fixed by commit: commit 2db9dbf71bf98d02a0bf33e798e5bfd2a9944696 Author: Bernd Edlinger Date: Fri Mar 20 20:27:24 2020 + proc: Use new infrastructure to fix deadlocks in execve bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17222ec410

possible deadlock in lock_trace (2)

Hello, syzbot found the following crash on: HEAD commit:444fe991 Merge tag 'riscv-for-linus-5.1-rc6' of git://git... git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=11b8f5d320 kernel config: https://syzkaller.appspot.com/x/.config?x=856fc6d0fbbeede9

Re: possible deadlock in lock_trace

On Thu, Nov 30, 2017 at 10:39:02AM -0800, syzbot wrote: > This bug is generated by a dumb bot. It may contain errors. > See https://goo.gl/tpsmEJ for details. > Direct all questions to syzkal...@googlegroups.com. > Please credit me with: Reported-by: syzbot > > syzbot

Re: possible deadlock in lock_trace

On Thu, Nov 30, 2017 at 10:39:02AM -0800, syzbot wrote: > This bug is generated by a dumb bot. It may contain errors. > See https://goo.gl/tpsmEJ for details. > Direct all questions to syzkal...@googlegroups.com. > Please credit me with: Reported-by: syzbot > > syzbot will keep track of this bug

Re: possible deadlock in lock_trace

On Thu, Nov 30, 2017 at 10:39:02AM -0800, syzbot wrote: > > syzbot will keep track of this bug report. > Once a fix for this bug is committed, please reply to this email with: > #syz fix: exact-commit-title > To mark this as a duplicate of another syzbot report, please reply with: > #syz dup:

Re: possible deadlock in lock_trace

On Thu, Nov 30, 2017 at 10:39:02AM -0800, syzbot wrote: > > syzbot will keep track of this bug report. > Once a fix for this bug is committed, please reply to this email with: > #syz fix: exact-commit-title > To mark this as a duplicate of another syzbot report, please reply with: > #syz dup: