[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID:
<SEZPR01MB5894794E69717A19DAA68BAEDDB62@SEZPR01MB5894.apcprd01.prod.exchangelabs.com>
Date: Sun, 28 Jul 2024 23:08:38 +0530
From: Mukesh Kumar Chaurasiya <mchauras@...mail.com>
To: buckzhang1212@...h.net
Cc: Ingo Molnar <mingo@...hat.com>, Peter Zijlstra <peterz@...radead.org>,
Juri Lelli <juri.lelli@...hat.com>, Vincent Guittot <vincent.guittot@...aro.org>,
Dietmar Eggemann <dietmar.eggemann@....com>, Steven Rostedt <rostedt@...dmis.org>,
Ben Segall <bsegall@...gle.com>, Mel Gorman <mgorman@...e.de>,
Daniel Bristot de Oliveira <bristot@...hat.com>, Valentin Schneider <vschneid@...hat.com>,
Nathan Chancellor <nathan@...nel.org>, Nick Desaulniers <ndesaulniers@...gle.com>,
Bill Wendling <morbo@...gle.com>, Justin Stitt <justinstitt@...gle.com>, llvm@...ts.linux.dev,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] sched:add panic to remind that wake_q_node should be
WAKE_Q_TAIL when emtpy
On Wed, Jul 17, 2024 at 09:19:01AM -0700, buckzhang1212@...h.net wrote:
> From: "weihui.zhang" <buckzhang1212@...h.net>
>
> Here is a kernel exception ,wake_q_node is NULL.
> when wake_q_node empty ,it must be WAKE_Q_TAIL instead of NULL Logically.
> Maybe a hardware bitflip corrupted the node ,add panic to call attention.
Hey,
is there a way to recreate this crash?
Regards,
Mukesh
Powered by blists - more mailing lists