[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231017141326.GB1599@noisy.programming.kicks-ass.net>
Date: Tue, 17 Oct 2023 16:13:26 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Aleksandr Nogikh <nogikh@...gle.com>
Cc: syzbot <syzbot+f78380e4eae53c64125c@...kaller.appspotmail.com>,
Benjamin Segall <bsegall@...gle.com>,
linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com,
tglx@...utronix.de, Dmitry Vyukov <dvyukov@...gle.com>
Subject: Re: [syzbot] [kernel?] possible deadlock in console_flush_all (2)
On Tue, Oct 17, 2023 at 12:06:12PM +0200, Aleksandr Nogikh wrote:
> This is currently causing more than 50% daily crashes on syzbot:
>
> https://syzkaller.appspot.com/upstream/graph/crashes
>
> It began to appear after next-20231004. Judging by the diff between
> next-20231003 and next-20231004, it looks like quite a few changes to
> kernel/sched were merged in between. Could it be caused by any of
> those?
> > EEVDF scheduling fail, picking leftmost
That was in next for a little bit, can you still reproduce with current
next?
Powered by blists - more mailing lists