linux-kernel - linux-next: build failure in Linus' 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 for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20170918093448.359d25c4@canb.auug.org.au>
Date:   Mon, 18 Sep 2017 09:34:48 +1000
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     Linux-Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        "Jan H. Schönherr" 
        <jschoenh@...zon.de>, Paolo Bonzini <pbonzini@...hat.com>
Subject: linux-next: build failure in Linus' tree

Hi Linus,

With just your tree, today's linux-next build (powerpc ppc64_defconfig)
failed like this:

arch/powerpc/kvm/../../../virt/kvm/eventfd.c: In function 'kvm_irqfd':
arch/powerpc/kvm/../../../virt/kvm/eventfd.c:568:19: error: 'KVM_MAX_IRQ_ROUTES' undeclared (first use in this function)
  if (args->gsi >= KVM_MAX_IRQ_ROUTES)
                   ^

Caused by commit

  36ae3c0a36b7 ("KVM: Don't accept obviously wrong gsi values via KVM_IRQFD")

KVM_MAX_IRQ_ROUTES is only defined when CONFIG_HAVE_KVM_IRQ_ROUTING is
defined (which for PowerPC is only when CONFIG_KVM_MPIC is defined which
depends on CONFIG_E500).

I have just reverted that commit for today.

-- 
Cheers,
Stephen Rothwell