linux-kernel - Re: linux-next: qemu boot failure after merge of the tip tree

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: <20210215095651.GC2185387@gmail.com>
Date:   Mon, 15 Feb 2021 10:56:51 +0100
From:   Ingo Molnar <mingo@...nel.org>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Peter Zijlstra <peterz@...radead.org>,
        Valentin Schneider <valentin.schneider@....com>,
        Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: qemu boot failure after merge of the tip tree


* Stephen Rothwell <sfr@...b.auug.org.au> wrote:

> Hi Peter,
> 
> On Mon, 1 Feb 2021 15:40:12 +0100 Peter Zijlstra <peterz@...radead.org> wrote:
> >
> > On Mon, Feb 01, 2021 at 01:04:30PM +0000, Valentin Schneider wrote:
> > > On 01/02/21 20:09, Stephen Rothwell wrote:  
> > > > Hi all,
> > > >  
> > > 
> > > Hi Stephen,
> > >   
> > > > After merging the tip tree, today's linux-next qemu boot test (powerpc
> > > > pseries_le_defconfig) failed like this:  
> > > 
> > > In case you haven't seen it, Dietmar did the dirty work and fixed my fail
> > > at
> > > 
> > >   http://lore.kernel.org/r/6000e39e-7d28-c360-9cd6-8798fd22a9bf@arm.com  
> > 
> > Right, picked that up, I'll try and push it before the next next ;-)
> 
> This fix has not reached the tip auto-latest branch yet and so is not in 
> linux-next.

This fix should be there now as:

  e972d92d52a1: ("sched/topology: Fix sched_domain_topology_level alloc in sched_init_numa()")

Thanks,

	Ingo