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]
Message-ID: <20210209155638.3581111a@canb.auug.org.au>
Date:   Tue, 9 Feb 2021 15:56:38 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Paolo Bonzini <pbonzini@...hat.com>
Cc:     KVM <kvm@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the kvm tree

Hi Paolo,

On Mon, 8 Feb 2021 06:48:32 +1100 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> On Fri, 5 Feb 2021 11:08:39 +0100 Paolo Bonzini <pbonzini@...hat.com> wrote:
> >
> > On 05/02/21 06:02, Stephen Rothwell wrote:  
> > > 
> > > After merging the kvm tree, today's linux-next build (powerpc
> > > ppc64_defconfig) failed like this:
> > > 
> > > ERROR: modpost: ".follow_pte" [arch/powerpc/kvm/kvm.ko] undefined!
> > > 
> > > Caused by commit
> > > 
> > >    bd2fae8da794 ("KVM: do not assume PTE is writable after follow_pfn")
> > > 
> > > follow_pte is not EXPORTed.
> > > 
> > > I have used the kvm tree from next-20210204 for today.
> > >     
> > 
> > Stephen, can you squash in the following for the time being?  
> 
> Wiil do.  I will drop it when it no longer applies.

I am still applying this patch.

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ