From: Avi Kivity <avi@qumranet.com>
To: Amit Shah <amit.shah@qumranet.com>
Cc: "Yang, Sheng" <sheng.yang@intel.com>, kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: Fix wrong KVM_GET_LAPIC
Date: Wed, 20 Aug 2008 10:10:57 +0300 [thread overview]
Message-ID: <48ABC381.4090600@qumranet.com> (raw)
In-Reply-To: <200808201212.09946.amit.shah@qumranet.com>
Amit Shah wrote:
> * On Monday 18 Aug 2008 08:45:40 Yang, Sheng wrote:
>
>> From a8ca7dd8f5fe0125e7b7d0a21f5caddacd754911 Mon Sep 17 00:00:00 2001
>> From: Sheng Yang <sheng.yang@intel.com>
>> Date: Mon, 18 Aug 2008 11:04:22 +0800
>> Subject: [PATCH] KVM: Fix wrong KVM_GET_LAPIC
>>
>> Which caused migration fail in recent commits.
>>
>> Signed-off-by: Sheng Yang <sheng.yang@intel.com>
>> ---
>> arch/x86/kvm/x86.c | 2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
>> index ee005a6..4a03375 100644
>> --- a/arch/x86/kvm/x86.c
>> +++ b/arch/x86/kvm/x86.c
>> @@ -1555,7 +1555,7 @@ long kvm_arch_vcpu_ioctl(struct file *filp,
>> if (r)
>> goto out;
>> r = -EFAULT;
>> - if (copy_to_user(argp, &lapic, sizeof lapic))
>> + if (copy_to_user(argp, lapic, sizeof(struct kvm_lapic_state)))
>>
>
> We're passing the structure instead of the pointer
'lapic' is now a pointer to a struct kvm_lapic_state.
> and this leads to build
> break with the tip on kvm.git.
>
>
Builds for me. Please double check.
> What's the point of this change anyway?
>
Fixing save/restore, which got broken by the stack usage reduction patches.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2008-08-20 7:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-18 3:15 [PATCH] KVM: Fix wrong KVM_GET_LAPIC Yang, Sheng
2008-08-18 10:08 ` Avi Kivity
2008-08-20 6:42 ` Amit Shah
2008-08-20 7:10 ` Avi Kivity [this message]
2008-08-20 9:17 ` Amit Shah
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=48ABC381.4090600@qumranet.com \
--to=avi@qumranet.com \
--cc=amit.shah@qumranet.com \
--cc=kvm@vger.kernel.org \
--cc=sheng.yang@intel.com \
/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.