From: Peter Zijlstra <peterz@infradead.org>
To: Sergei Trofimovich <slyich@gmail.com>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
yu.c.chen@intel.com, wuyun.abel@bytedance.com
Subject: Re: 6.8 to 6.9.0-rc3: kernel NULL pointer dereference in pick_next_task_fair+0x89
Date: Mon, 15 Apr 2024 12:59:07 +0200 [thread overview]
Message-ID: <20240415105907.GL40213@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <ZhuYyrh3mweP_Kd8@nz.home>
On Sun, Apr 14, 2024 at 09:50:18AM +0100, Sergei Trofimovich wrote:
> Hi kernel/sched/ maintainers!
>
> Over past few days my machines started OOpsing when a nightly kernel
> build starts. I don't have a reliable reproducer. The builder should use
> `idle` CPU scheduling policy.
>
Thanks for the report, some of us have been chasing this ghost for a
little while and so far it has proven elusive because it's very hard to
reliably reproduce.
I'll go try with your approach.
next prev parent reply other threads:[~2024-04-15 10:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-14 8:50 Sergei Trofimovich
2024-04-15 10:59 ` Peter Zijlstra [this message]
2024-04-16 6:18 Igor Raits
2024-04-16 16:23 ` Peter Zijlstra
2024-04-16 16:46 ` Igor Raits
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=20240415105907.GL40213@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=slyich@gmail.com \
--cc=wuyun.abel@bytedance.com \
--cc=yu.c.chen@intel.com \
/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
Powered by JetHome