Re: [syzbot] possible deadlock in console_unlock (2)

Sergey Senozhatsky
2022-06-27T07:39:17Z

On (22/06/27 09:11), Dmitry Vyukov wrote:
> > syzbot suspects this issue was fixed by commit:
> >
> > commit faebd693c59387b7b765fab64b543855e15a91b4
> > Author: John Ogness <john.ogness@linutronix.de>
> > Date: Thu Apr 21 21:22:36 2022 +0000
> >
> > printk: rename cpulock functions
> >
> > bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17ed359bf00000
> > start commit: aa051d36ce4a Merge tag 'for-linus-2022052401' of git://git..
> > git tree: upstream
> > kernel config: https://syzkaller.appspot.com/x/.config?x=6c31e1555a4c59f3
> > dashboard link: https://syzkaller.appspot.com/bug?extid=0b7c8bfd17c00d016fb4
> > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16a5aad6f00000
> > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16d697c3f00000
> >
> > If the result looks correct, please mark the issue as fixed by replying with:
> >
> > #syz fix: printk: rename cpulock functions
> >
> > For information about bisection process see: https://goo.gl/tpsmEJ#bisection
>
>
> I guess this is also:
>
> #syz fix: printk: add kthread console printers

Dmirty, we have reverted console kthreads for the time being.