linux-kernel - Re: [tip:sched/core] BUILD SUCCESS 3387ce4d8a5f2956fab827edf499fe6780e83faa

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: <20220324175801.GJ8939@worktop.programming.kicks-ass.net>
Date:   Thu, 24 Mar 2022 18:58:01 +0100
From:   Peter Zijlstra <peterz@...radead.org>
To:     "Chen, Rong A" <rong.a.chen@...el.com>
Cc:     Nathan Chancellor <nathan@...nel.org>,
        kernel test robot <lkp@...el.com>, x86-ml <x86@...nel.org>,
        linux-kernel@...r.kernel.org
Subject: Re: [tip:sched/core] BUILD SUCCESS
 3387ce4d8a5f2956fab827edf499fe6780e83faa

On Tue, Mar 22, 2022 at 10:39:41AM +0800, Chen, Rong A wrote:
> On 3/22/2022 7:17 AM, Nathan Chancellor wrote:
> > Hello,
> > 
> > On Tue, Mar 22, 2022 at 06:36:16AM +0800, kernel test robot wrote:
> > > tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git sched/core
> > > branch HEAD: 3387ce4d8a5f2956fab827edf499fe6780e83faa  headers/prep: Fix header to build standalone: <linux/psi.h>
> > > 
> > > elapsed time: 730m
> > > 
> > > configs tested: 114
> > > configs skipped: 3
> > > 
> > > The following configs have been built successfully.
> > > More configs may be tested in the coming days.
> > > 
> > > gcc tested configs:
> > ...
> > > arm                              allyesconfig
> > > arm                              allmodconfig
> > 

> > Are you sure these configurations built sucessfully?

...

> Thanks for your reminding, the problem commit is 4ff8f2ca6ccd
> ("sched/headers: Reorganize, clean up and optimize kernel/sched/sched.h
> dependencies"),
> the bot has sent two build reports related to it:
> 
>   https://lore.kernel.org/all/202203152116.qphmikIZ-lkp@intel.com/
>   https://lore.kernel.org/all/202203152144.uFQqgVUf-lkp@intel.com/
> 
> and more reports were stopped to avoid too many noise, like below one:

...

> We'll adjust the strategy avoid blocking some important reports.

Oh *PLEASE* never report a branch as building if there's errors.
It could be I (force) push a branch multiple times before I get any
0day reports back (0day has gotten *soooo* slow) so I only ever look at
the latest report -- possibly days later.

If you then falsly report the branch as being good, because you're
suppressing errors, things *will* go bad.