From: Peter Zijlstra <peterz@infradead.org>
To: Aleksandr Nogikh <nogikh@google.com>
Cc: syzbot <syzbot+f78380e4eae53c64125c@syzkaller.appspotmail.com>,
Benjamin Segall <bsegall@google.com>,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, Dmitry Vyukov <dvyukov@google.com>
Subject: Re: [syzbot] [kernel?] possible deadlock in console_flush_all (2)
Date: Tue, 17 Oct 2023 16:13:26 +0200 [thread overview]
Message-ID: <20231017141326.GB1599@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <CANp29Y61NUOC1CDOzNs_euoFCG-tX1TGFEfro2PuvBEhGqEC3Q@mail.gmail.com>
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?
next prev parent reply other threads:[~2023-10-17 14:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-08 6:28 syzbot
2023-10-17 10:06 ` Aleksandr Nogikh
2023-10-17 14:13 ` Peter Zijlstra [this message]
2023-10-17 13:07 ` [syzbot] [ext4?] " syzbot
2023-10-17 14:16 ` Peter Zijlstra
2023-10-17 14:28 ` Aleksandr Nogikh
2024-03-05 14:05 ` [syzbot] [kernel?] " Tetsuo Handa
2024-03-05 15:21 ` [syzbot] [serial?] " syzbot
2024-03-20 6:50 ` [syzbot] [kernel?] " Tetsuo Handa
2024-03-20 6:56 ` Alexei Starovoitov
2024-03-20 7:04 ` Tetsuo Handa
2024-03-20 7:12 ` Alexei Starovoitov
2024-03-20 7:30 ` Tetsuo Handa
2024-03-20 8:47 ` Alexei Starovoitov
2024-03-27 11:05 ` John Ogness
2024-03-27 14:25 ` Tetsuo Handa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231017141326.GB1599@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bsegall@google.com \
--cc=dvyukov@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nogikh@google.com \
--cc=syzbot+f78380e4eae53c64125c@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®