All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 115081] New: arch/x86/kvm/vmx.c:8719: Error: symbol `vmx_return' is already defined
Date: Mon, 21 Mar 2016 23:16:05 +0000	[thread overview]
Message-ID: <bug-115081-28872@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 115081
           Summary: arch/x86/kvm/vmx.c:8719: Error: symbol `vmx_return' is
                    already defined
           Product: Virtualization
           Version: unspecified
    Kernel Version: 4.5
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: blocking
          Priority: P1
         Component: kvm
          Assignee: virtualization_kvm@kernel-bugs.osdl.org
          Reporter: lkml@tlinx.org
        Regression: Yes

Created attachment 210151
  --> https://bugzilla.kernel.org/attachment.cgi?id=210151&action=edit
make output

I am getting an error in compiling the 4.5 sources (patched up from 4.4).

After getting the error, I d/l'd the full source and compared the file above --
and it was identical to the above file.

I searched for the symbol "vmx_return" under the "arch/x86" dir, but only found
it referenced in the above ".c" file.

I didn't get this error in the previous 4.4 line (I made 4.4.1 & 4.4.3) and
current kernel-uname shows:

Linux Ishtar 4.4.3-Isht-Van #2 SMP PREEMPT Thu Feb 25 22:53:27 PST 2016 x86_64
x86_64 x86_64 GNU/Linux

At this point, I can't see why I'd get the above error.  Make output and
".config" attached.

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

             reply	other threads:[~2016-03-21 23:16 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-21 23:16 bugzilla-daemon [this message]
2016-03-21 23:17 ` [Bug 115081] arch/x86/kvm/vmx.c:8719: Error: symbol `vmx_return' is already defined bugzilla-daemon
2016-03-23 20:09 ` bugzilla-daemon
2016-03-24  2:46 ` bugzilla-daemon
2016-03-24  3:54 ` bugzilla-daemon
2016-03-24  4:19 ` bugzilla-daemon
2016-03-24  8:30 ` bugzilla-daemon
2016-03-24 13:31 ` bugzilla-daemon
2016-03-24 13:34 ` bugzilla-daemon
2016-03-25 17:11 ` bugzilla-daemon
2016-03-25 17:19 ` bugzilla-daemon
2016-03-29  9:48 ` bugzilla-daemon
2016-03-29 16:44 ` bugzilla-daemon
2016-03-29 16:45 ` bugzilla-daemon
2016-03-29 16:45 ` bugzilla-daemon
2016-03-29 16:54 ` bugzilla-daemon
2016-03-29 16:54 ` bugzilla-daemon
2016-03-29 16:55 ` bugzilla-daemon
2016-03-29 16:57 ` bugzilla-daemon
2016-03-29 17:18 ` bugzilla-daemon
2016-03-29 17:27 ` bugzilla-daemon
2016-03-29 17:55 ` bugzilla-daemon
2016-03-30  9:18 ` bugzilla-daemon
2016-03-31  3:12 ` bugzilla-daemon
2016-03-31  3:13 ` bugzilla-daemon

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-115081-28872@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.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 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.