All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
	kvm-ppc@vger.kernel.org
Subject: Re: Build regressions/improvements in v4.2-rc8
Date: Wed, 26 Aug 2015 09:03:02 +0000	[thread overview]
Message-ID: <55DD80C6.7030400@suse.de> (raw)
In-Reply-To: <CAMuHMdVomabvJOLLJ-tJs6KjL05YpH3zLkyrPbyEghe=WvOVkA@mail.gmail.com>



On 24.08.15 10:36, Geert Uytterhoeven wrote:
> On Mon, Aug 24, 2015 at 10:34 AM, Geert Uytterhoeven
> <geert@linux-m68k.org> wrote:
>> JFYI, when comparing v4.2-rc8[1] to v4.2-rc7[3], the summaries are:
>>   - build errors: +4/-7
> 
> 4 regressions:
>   + /home/kisskb/slave/src/include/linux/kvm_host.h: error: array
> subscript is above array bounds [-Werror=array-bounds]:  => 430:19
>     (arch/powerpc/kvm/book3s_64_mmu.c: In function 'kvmppc_mmu
> _book3s_64_tlbie':)
> 
> powerpc-randconfig (seen before in a v3.15-rc1 build?)

I'm not quite sure what's going wrong here. The code in question does

  kvm_for_each_vcpu(i, v, vcpu->kvm)
    kvmppc_mmu_pte_vflush(v, va >> 12, mask);

and IIUC the thing we're potentially running over on would be
kvm->vcpus[i]. But that one is bound by the kvm_for_each_vcpu loop, no?


Alex

WARNING: multiple messages have this Message-ID (diff)
From: Alexander Graf <agraf@suse.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
	kvm-ppc@vger.kernel.org
Subject: Re: Build regressions/improvements in v4.2-rc8
Date: Wed, 26 Aug 2015 11:03:02 +0200	[thread overview]
Message-ID: <55DD80C6.7030400@suse.de> (raw)
In-Reply-To: <CAMuHMdVomabvJOLLJ-tJs6KjL05YpH3zLkyrPbyEghe=WvOVkA@mail.gmail.com>



On 24.08.15 10:36, Geert Uytterhoeven wrote:
> On Mon, Aug 24, 2015 at 10:34 AM, Geert Uytterhoeven
> <geert@linux-m68k.org> wrote:
>> JFYI, when comparing v4.2-rc8[1] to v4.2-rc7[3], the summaries are:
>>   - build errors: +4/-7
> 
> 4 regressions:
>   + /home/kisskb/slave/src/include/linux/kvm_host.h: error: array
> subscript is above array bounds [-Werror=array-bounds]:  => 430:19
>     (arch/powerpc/kvm/book3s_64_mmu.c: In function 'kvmppc_mmu
> _book3s_64_tlbie':)
> 
> powerpc-randconfig (seen before in a v3.15-rc1 build?)

I'm not quite sure what's going wrong here. The code in question does

  kvm_for_each_vcpu(i, v, vcpu->kvm)
    kvmppc_mmu_pte_vflush(v, va >> 12, mask);

and IIUC the thing we're potentially running over on would be
kvm->vcpus[i]. But that one is bound by the kvm_for_each_vcpu loop, no?


Alex

  reply	other threads:[~2015-08-26  9:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-24  8:34 Build regressions/improvements in v4.2-rc8 Geert Uytterhoeven
2015-08-24  8:36 ` Geert Uytterhoeven
2015-08-24  8:36   ` Geert Uytterhoeven
2015-08-24  8:36   ` Geert Uytterhoeven
2015-08-26  9:03   ` Alexander Graf [this message]
2015-08-26  9:03     ` Alexander Graf

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55DD80C6.7030400@suse.de \
    --to=agraf@suse.de \
    --cc=geert@linux-m68k.org \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.