From: "tip-bot2 for Wei Liu" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Boqun Feng <boqun.feng@gmail.com>, Wei Liu <wei.liu@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>, x86 <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: [tip: x86/entry] x86/hyperv: Use the correct target for alloc_intr_gate()
Date: Thu, 28 May 2020 10:13:27 -0000 [thread overview]
Message-ID: <159066080714.17951.8989624032770050231.tip-bot2@tip-bot2> (raw)
In-Reply-To: =?utf-8?q?=3C20200527120918=2Ely5vuhvxzqesdt6j=40liuwe-devbox-d?= =?utf-8?q?ebian-v2=2Ej3c5onc20sse1dnehy4noqpfcg=2Ezx=2Einternal=2Ecloud?= =?utf-8?q?app=2Enet=3E?=
The following commit has been merged into the x86/entry branch of tip:
Commit-ID: 4bcffde74b6a2ba992a0617bb6b9be054e7f89a2
Gitweb: https://git.kernel.org/tip/4bcffde74b6a2ba992a0617bb6b9be054e7f89a2
Author: Wei Liu <wei.liu@kernel.org>
AuthorDate: Wed, 27 May 2020 12:09:18
Committer: Thomas Gleixner <tglx@linutronix.de>
CommitterDate: Thu, 28 May 2020 12:01:24 +02:00
x86/hyperv: Use the correct target for alloc_intr_gate()
The idtentry rework causes a boot crash, by erroneously using the C entry
point to allocate the interrupt gate for the HYPERVISOR_CALLBACK_VECTOR.
Use the ASM entry point to cure this.
[ tglx: Changelog as it was too late to fold in ]
Fixes: 824ad0f5f390 ("x86/entry: Convert various hypervisor vectors to IDTENTRY_SYSVEC")
Reported-by: Boqun Feng <boqun.feng@gmail.com>
Signed-off-by: Wei Liu <wei.liu@kernel.org>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Tested-by: Boqun Feng <boqun.feng@gmail.com>
Link: https://lkml.kernel.org/r/20200527120918.ly5vuhvxzqesdt6j@liuwe-devbox-debian-v2.j3c5onc20sse1dnehy4noqpfcg.zx.internal.cloudapp.net
---
arch/x86/kernel/cpu/mshyperv.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/kernel/cpu/mshyperv.c b/arch/x86/kernel/cpu/mshyperv.c
index a103e1c..af94f05 100644
--- a/arch/x86/kernel/cpu/mshyperv.c
+++ b/arch/x86/kernel/cpu/mshyperv.c
@@ -327,7 +327,7 @@ static void __init ms_hyperv_init_platform(void)
x86_platform.apic_post_init = hyperv_init;
hyperv_setup_mmu_ops();
/* Setup the IDT for hypervisor callback */
- alloc_intr_gate(HYPERVISOR_CALLBACK_VECTOR, sysvec_hyperv_callback);
+ alloc_intr_gate(HYPERVISOR_CALLBACK_VECTOR, asm_sysvec_hyperv_callback);
/* Setup the IDT for reenlightenment notifications */
if (ms_hyperv.features & HV_X64_ACCESS_REENLIGHTENMENT) {
reply other threads:[~2020-05-28 10:13 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=159066080714.17951.8989624032770050231.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=boqun.feng@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=wei.liu@kernel.org \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).