linux-kernel - Re: [PATCH] sched/fair: Fix inaccurate h_nr_runnable accounting with delayed dequeue

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: <20250120084441.17746-1-vineethr@linux.ibm.com>
Date: Mon, 20 Jan 2025 14:14:41 +0530
From: Madadi Vineeth Reddy <vineethr@...ux.ibm.com>
To: vineethr@...ux.ibm.com
Cc: bsegall@...gle.com, dietmar.eggemann@....com, gautham.shenoy@....com,
        juri.lelli@...hat.com, kprateek.nayak@....com,
        linux-kernel@...r.kernel.org, mgorman@...e.de, mingo@...hat.com,
        peterz@...radead.org, rostedt@...dmis.org, swapnil.sapkal@....com,
        vincent.guittot@...aro.org, vschneid@...hat.com
Subject: Re: [PATCH] sched/fair: Fix inaccurate h_nr_runnable accounting with delayed dequeue

> However, I was unable to trigger the WARN_ON by running hackbench in a
> cgroup without the patch. Could you please share the specific test
> scenario or configuration you used to reproduce it?

My mistake: SCHED_WARN_ON is a WARN_ONCE, so I had to clear it before
running hackbench to ensure the WARN_ON could be triggered again.

Now I am able to trigger the WARN_ON in the unpatched kernel while
running hackbench after executing `echo 1 > /sys/kernel/debug/clear_warn_once`
following the initial warning during the boot process. I have verified
that the patched kernel fixes the issue.

Thanks,
Madadi Vineeth Reddy