public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 215995] New: error: array subscript 32 is above array bounds of ‘long unsigned int[17]’
Date: Wed, 18 May 2022 06:45:45 +0000	[thread overview]
Message-ID: <bug-215995-28872@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=215995

            Bug ID: 215995
           Summary: error: array subscript 32 is above array bounds of
                    ‘long unsigned int[17]’
           Product: Virtualization
           Version: unspecified
    Kernel Version: 5.18.0-rc7
          Hardware: AMD
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: blocking
          Priority: P1
         Component: kvm
          Assignee: virtualization_kvm@kernel-bugs.osdl.org
          Reporter: ionut_n2001@yahoo.com
        Regression: No

Hi Kernel Team,

Today i notice one error on compiling kernel in kvm area.

Error:
  CC [M]  arch/x86/kvm/svm/svm_onhyperv.o
  CHK     kernel/kheaders_data.tar.xz
In function ‘reg_read’,
    inlined from ‘reg_rmw’ at arch/x86/kvm/emulate.c:266:2,
    inlined from ‘decode_register’ at arch/x86/kvm/emulate.c:985:7:
arch/x86/kvm/emulate.c:254:27: error: array subscript 32 is above array bounds
of ‘long unsigned int[17]’ [-Werror=array-bounds]
  254 |         return ctxt->_regs[nr];
      |                ~~~~~~~~~~~^~~~
In file included from arch/x86/kvm/emulate.c:23:
arch/x86/kvm/kvm_emulate.h: In function ‘decode_register’:
arch/x86/kvm/kvm_emulate.h:366:23: note: while referencing ‘_regs’
  366 |         unsigned long _regs[NR_VCPU_REGS];
      |                       ^~~~~
cc1: all warnings being treated as errors
make[4]: *** [scripts/Makefile.build:288: arch/x86/kvm/emulate.o] Error 1
make[4]: *** Waiting for unfinished jobs....
  CHK     include/generated/compile.h
make[3]: *** [scripts/Makefile.build:550: arch/x86/kvm] Error 2
make[2]: *** [Makefile:1882: arch/x86] Error 2
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [scripts/Makefile.package:66: binrpm-pkg] Error 2
make: *** [Makefile:1588: binrpm-pkg] Error 2


cat /etc/os-release 
NAME="openSUSE Tumbleweed"
# VERSION="20220516"
ID="opensuse-tumbleweed"
ID_LIKE="opensuse suse"
VERSION_ID="20220516"
PRETTY_NAME="openSUSE Tumbleweed"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:tumbleweed:20220516"
BUG_REPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org/"
DOCUMENTATION_URL="https://en.opensuse.org/Portal:Tumbleweed"
LOGO="distributor-logo-Tumbleweed"

gcc --version
gcc (SUSE Linux) 12.1.0
Copyright (C) 2022 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

ldd --version
ldd (GNU libc) 2.35
Copyright (C) 2022 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Written by Roland McGrath and Ulrich Drepper.

CONFIG_KVM_WERROR=y

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

                 reply	other threads:[~2022-05-18  6:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bug-215995-28872@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=kvm@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox