From: Marcelo Tosatti <mtosatti@redhat.com>
To: Dave Hansen <dave@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Gleb Natapov <gleb@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Rik van Riel <riel@redhat.com>
Subject: Re: [PATCH 5/5] fix kvm's use of __pa() on percpu areas
Date: Tue, 22 Jan 2013 22:08:20 -0200 [thread overview]
Message-ID: <20130123000820.GA27204@amt.cnet> (raw)
In-Reply-To: <20130122212435.4905663F@kernel.stglabs.ibm.com>
On Tue, Jan 22, 2013 at 01:24:35PM -0800, Dave Hansen wrote:
>
> In short, it is illegal to call __pa() on an address holding
> a percpu variable. This replaces those __pa() calls with
> slow_virt_to_phys(). All of the cases in this patch are
> in boot time (or CPU hotplug time at worst) code, so the
> slow pagetable walking in slow_virt_to_phys() is not expected
> to have a performance impact.
>
> The times when this actually matters are pretty obscure
> (certain 32-bit NUMA systems), but it _does_ happen. It is
> important to keep KVM guests working on these systems because
> the real hardware is getting harder and harder to find.
>
> This bug manifested first by me seeing a plain hang at boot
> after this message:
>
> CPU 0 irqstacks, hard=f3018000 soft=f301a000
>
> or, sometimes, it would actually make it out to the console:
>
> [ 0.000000] BUG: unable to handle kernel paging request at ffffffff
>
> I eventually traced it down to the KVM async pagefault code.
> This can be worked around by disabling that code either at
> compile-time, or on the kernel command-line.
>
> The kvm async pagefault code was injecting page faults in
> to the guest which the guest misinterpreted because its
> "reason" was not being properly sent from the host.
>
> The guest passes a physical address of an per-cpu async page
> fault structure via an MSR to the host. Since __pa() is
> broken on percpu data, the physical address it sent was
> bascially bogus and the host went scribbling on random data.
> The guest never saw the real reason for the page fault (it
> was injected by the host), assumed that the kernel had taken
> a _real_ page fault, and panic()'d. The behavior varied,
> though, depending on what got corrupted by the bad write.
>
> Signed-off-by: Dave Hansen <dave@linux.vnet.ibm.com>
> Acked-by: Rik van Riel <riel@redhat.com>
> ---
>
> linux-2.6.git-dave/arch/x86/kernel/kvm.c | 9 +++++----
> linux-2.6.git-dave/arch/x86/kernel/kvmclock.c | 4 ++--
> 2 files changed, 7 insertions(+), 6 deletions(-)
Reviewed-by: Marcelo Tosatti <mtosatti@redhat.com>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Marcelo Tosatti <mtosatti@redhat.com>
To: Dave Hansen <dave@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Gleb Natapov <gleb@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Rik van Riel <riel@redhat.com>
Subject: Re: [PATCH 5/5] fix kvm's use of __pa() on percpu areas
Date: Tue, 22 Jan 2013 22:08:20 -0200 [thread overview]
Message-ID: <20130123000820.GA27204@amt.cnet> (raw)
In-Reply-To: <20130122212435.4905663F@kernel.stglabs.ibm.com>
On Tue, Jan 22, 2013 at 01:24:35PM -0800, Dave Hansen wrote:
>
> In short, it is illegal to call __pa() on an address holding
> a percpu variable. This replaces those __pa() calls with
> slow_virt_to_phys(). All of the cases in this patch are
> in boot time (or CPU hotplug time at worst) code, so the
> slow pagetable walking in slow_virt_to_phys() is not expected
> to have a performance impact.
>
> The times when this actually matters are pretty obscure
> (certain 32-bit NUMA systems), but it _does_ happen. It is
> important to keep KVM guests working on these systems because
> the real hardware is getting harder and harder to find.
>
> This bug manifested first by me seeing a plain hang at boot
> after this message:
>
> CPU 0 irqstacks, hard=f3018000 soft=f301a000
>
> or, sometimes, it would actually make it out to the console:
>
> [ 0.000000] BUG: unable to handle kernel paging request at ffffffff
>
> I eventually traced it down to the KVM async pagefault code.
> This can be worked around by disabling that code either at
> compile-time, or on the kernel command-line.
>
> The kvm async pagefault code was injecting page faults in
> to the guest which the guest misinterpreted because its
> "reason" was not being properly sent from the host.
>
> The guest passes a physical address of an per-cpu async page
> fault structure via an MSR to the host. Since __pa() is
> broken on percpu data, the physical address it sent was
> bascially bogus and the host went scribbling on random data.
> The guest never saw the real reason for the page fault (it
> was injected by the host), assumed that the kernel had taken
> a _real_ page fault, and panic()'d. The behavior varied,
> though, depending on what got corrupted by the bad write.
>
> Signed-off-by: Dave Hansen <dave@linux.vnet.ibm.com>
> Acked-by: Rik van Riel <riel@redhat.com>
> ---
>
> linux-2.6.git-dave/arch/x86/kernel/kvm.c | 9 +++++----
> linux-2.6.git-dave/arch/x86/kernel/kvmclock.c | 4 ++--
> 2 files changed, 7 insertions(+), 6 deletions(-)
Reviewed-by: Marcelo Tosatti <mtosatti@redhat.com>
next prev parent reply other threads:[~2013-01-23 0:21 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 21:24 [PATCH 0/5] [v3] fix illegal use of __pa() in KVM code Dave Hansen
2013-01-22 21:24 ` Dave Hansen
2013-01-22 21:24 ` [PATCH 1/5] make DEBUG_VIRTUAL work earlier in boot Dave Hansen
2013-01-22 21:24 ` Dave Hansen
2013-01-26 1:51 ` [tip:x86/mm] x86, mm: Make " tip-bot for Dave Hansen
2013-01-22 21:24 ` [PATCH 2/5] pagetable level size/shift/mask helpers Dave Hansen
2013-01-22 21:24 ` Dave Hansen
2013-01-26 1:52 ` [tip:x86/mm] x86, mm: Pagetable " tip-bot for Dave Hansen
2013-01-22 21:24 ` [PATCH 3/5] use new pagetable helpers in try_preserve_large_page() Dave Hansen
2013-01-22 21:24 ` Dave Hansen
2013-01-26 1:53 ` [tip:x86/mm] x86, mm: Use " tip-bot for Dave Hansen
2013-01-22 21:24 ` [PATCH 4/5] create slow_virt_to_phys() Dave Hansen
2013-01-22 21:24 ` Dave Hansen
2013-01-26 1:54 ` [tip:x86/mm] x86, mm: Create slow_virt_to_phys() tip-bot for Dave Hansen
2013-01-22 21:24 ` [PATCH 5/5] fix kvm's use of __pa() on percpu areas Dave Hansen
2013-01-22 21:24 ` Dave Hansen
2013-01-23 0:08 ` Marcelo Tosatti [this message]
2013-01-23 0:08 ` Marcelo Tosatti
2013-01-26 1:56 ` [tip:x86/mm] x86, kvm: Fix " tip-bot for Dave Hansen
2013-01-25 23:15 ` [PATCH 0/5] [v3] fix illegal use of __pa() in KVM code Dave Hansen
2013-01-25 23:15 ` Dave Hansen
2013-02-24 21:28 ` Peter Hurley
2013-02-24 21:28 ` Peter Hurley
2013-02-25 8:30 ` Gleb Natapov
2013-02-25 8:30 ` Gleb Natapov
2013-02-25 14:42 ` Dave Hansen
2013-02-25 14:42 ` Dave Hansen
2013-02-26 12:45 ` Peter Hurley
2013-02-26 12:45 ` Peter Hurley
-- strict thread matches above, loose matches on Subject: below --
2013-01-21 17:52 [PATCH 0/5] " Dave Hansen
2013-01-21 17:52 ` [PATCH 5/5] fix kvm's use of __pa() on percpu areas Dave Hansen
2013-01-21 17:52 ` Dave Hansen
2013-01-21 18:38 ` H. Peter Anvin
2013-01-21 18:38 ` H. Peter Anvin
2013-01-21 18:59 ` Dave Hansen
2013-01-21 18:59 ` Dave Hansen
2013-01-21 19:22 ` H. Peter Anvin
2013-01-21 19:22 ` H. Peter Anvin
2013-01-21 19:02 ` Gleb Natapov
2013-01-21 19:02 ` Gleb Natapov
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=20130123000820.GA27204@amt.cnet \
--to=mtosatti@redhat.com \
--cc=dave@linux.vnet.ibm.com \
--cc=gleb@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.com \
--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 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.