lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <09e16088690e6577b60de489e6e52a3e5769f96f.camel@gmx.de>
Date: Tue, 01 Oct 2024 18:41:25 +0200
From: Mike Galbraith <efault@....de>
To: Vishal Chourasia <vishalc@...ux.ibm.com>
Cc: Peter Zijlstra <peterz@...radead.org>, linux-kernel@...r.kernel.org, 
 Ingo Molnar <mingo@...hat.com>, Vincent Guittot
 <vincent.guittot@...aro.org>, Juri Lelli <juri.lelli@...hat.com>, Dietmar
 Eggemann <dietmar.eggemann@....com>, Steven Rostedt <rostedt@...dmis.org>,
 Ben Segall <bsegall@...gle.com>, Mel Gorman <mgorman@...e.de>,  Valentin
 Schneider <vschneid@...hat.com>, luis.machado@....com
Subject: Re: sched/fair: Kernel panics in pick_next_entity

On Tue, 2024-10-01 at 19:38 +0530, Vishal Chourasia wrote:
>
> With the below changes, I don't see any warnings been printed on the
> console, along with it, there were no kernel panics

Darn.  I was hoping to quash the easily reproducible noisy avalanche of
doom to let elusive $subject through, that being way more interesting.

When I hit $subject, LTPs cfs_bandwidth01 was running, but there was no
warning prelude, box went straight to panic.  Trying to reproduce using
that testcase plus hackbench as efficacy booster produced lots of dying
box noise, but zero sneaky $subject instances before or after quash.

	-Mike

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ