linux-kernel - Re: [PATCH] sched/fair: Fix kernel build warning in test_idle

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] [day] [month] [year] [list]

Date:   Thu, 27 Feb 2020 14:00:57 +0000
From:   Mel Gorman <mgorman@...hsingularity.net>
To:     Lukasz Luba <lukasz.luba@....com>
Cc:     Valentin Schneider <valentin.schneider@....com>,
        linux-kernel@...r.kernel.org, mingo@...hat.com,
        peterz@...radead.org, vincent.guittot@...aro.org,
        dietmar.eggemann@....com
Subject: Re: [PATCH] sched/fair: Fix kernel build warning in
 test_idle_cores() for !SMT NUMA

On Thu, Feb 27, 2020 at 12:08:46PM +0000, Lukasz Luba wrote:
> Hi Valentin,
> 
> On 2/27/20 11:04 AM, Valentin Schneider wrote:
> > Hi Lukasz,
> > 
> > On 2/27/20 11:00 AM, Lukasz Luba wrote:
> > > Fix kernel build warning in kernel/sched/fair.c when CONFIG_SCHED_SMT is
> > > not set and CONFIG_NUMA_BALANCING is set.
> > > 
> > > kernel/sched/fair.c:1524:20: warning: ???test_idle_cores??? declared ???static??? but never defined [-Wunused-function]
> > > 
> > 
> > I've sent a similar fix yesterday at:
> > 
> > https://lore.kernel.org/lkml/20200226121244.7524-1-valentin.schneider@arm.com/
> > 
> 
> I've missed it. You are referring in the commit message to wrong change
> (probably HEAD of that branch), while when you try to bisect, it
> will point you to
> ff7db0bf24db sched/numa: Prefer using an idle CPU as a migration target
> instead of comparing tasks
> 
> I think Mel can simply resend the patches with correct build if Ingo
> is OK.
> 
> If Mel would decide to go with extended approach of ifdefs, then maybe
> it's also good to put in there  numa_idle_core(), which actually uses
> these test_idle_cores() and is_core_idle()
> 

I preferred the first fix. I'll send just it on with an editted changelog
to identify the exact patch that caused the problem. Ingo will hopefully
let me know if he prefers to pick up the fix on top or a resend of the
series with the fix folded in.

-- 
Mel Gorman
SUSE Labs