From: Jan Kiszka <jan.kiszka@siemens.com>
To: Avi Kivity <avi@redhat.com>
Cc: "Kirill A. Shutemov" <kirill@shutemov.name>,
Christoph Lameter <cl@linux.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org,
Pekka Enberg <penberg@cs.helsinki.fi>
Subject: Re: BUG: sleeping function called from invalid context at mm/slub.c:793
Date: Thu, 13 Jan 2011 13:59:03 +0100 [thread overview]
Message-ID: <4D2EF717.8080604@siemens.com> (raw)
In-Reply-To: <4D2C3115.9030301@redhat.com>
Am 11.01.2011 11:29, Avi Kivity wrote:
> Please try out the attached patch.
>
> From f3a6041b5bb3bf7c88f9694a66d7f34be2f78845 Mon Sep 17 00:00:00 2001
> From: Avi Kivity <avi@redhat.com>
> Date: Tue, 11 Jan 2011 12:15:54 +0200
> Subject: [PATCH] KVM: Initialize fpu state in preemptible context
>
> init_fpu() (which is indirectly called by the fpu switching code) assumes
> it is in process context. Rather than makeing init_fpu() use an atomic
> allocation, which can cause a task to be killed, make sure the fpu is
> already initialized when we enter the run loop.
>
> Signed-off-by: Avi Kivity <avi@redhat.com>
> ---
> arch/x86/kernel/i387.c | 1 +
> arch/x86/kvm/x86.c | 3 +++
> 2 files changed, 4 insertions(+), 0 deletions(-)
>
> diff --git a/arch/x86/kernel/i387.c b/arch/x86/kernel/i387.c
> index 58bb239..e60c38c 100644
> --- a/arch/x86/kernel/i387.c
> +++ b/arch/x86/kernel/i387.c
> @@ -169,6 +169,7 @@ int init_fpu(struct task_struct *tsk)
> set_stopped_child_used_math(tsk);
> return 0;
> }
> +EXPORT_SYMBOL_GPL(init_fpu);
>
> /*
> * The xstateregs_active() routine is the same as the fpregs_active() routine,
> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> index 8652643..fd93cda 100644
> --- a/arch/x86/kvm/x86.c
> +++ b/arch/x86/kvm/x86.c
> @@ -5351,6 +5351,9 @@ int kvm_arch_vcpu_ioctl_run(struct kvm_vcpu *vcpu, struct kvm_run *kvm_run)
> int r;
> sigset_t sigsaved;
>
> + if (!tsk_used_math(current) && init_fpu(current))
> + return -ENOMEM;
> +
Could become a rainy day for the kvm-kmod maintainer:
For compat support on kernels without init_fpu exported yet, can I
trigger the same result by simply issuing an FPU instruction here so
that do_device_not_available will perform the allocation? Not really
nice, but it doesn't appear to me like there is any code path that would
complain about in-kernel FPU usage (provided we don't need math
emulation - which is quite likely).
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2011-01-13 12:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-10 10:54 BUG: sleeping function called from invalid context at mm/slub.c:793 Kirill A. Shutemov
2011-01-10 16:52 ` Christoph Lameter
2011-01-10 19:31 ` Kirill A. Shutemov
2011-01-11 9:49 ` Avi Kivity
2011-01-11 10:29 ` Avi Kivity
2011-01-11 11:13 ` Kirill A. Shutemov
2011-01-11 11:20 ` Pekka Enberg
2011-01-11 14:43 ` Christoph Lameter
2011-01-13 12:59 ` Jan Kiszka [this message]
2011-01-13 13:06 ` Avi Kivity
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=4D2EF717.8080604@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=avi@redhat.com \
--cc=cl@linux.com \
--cc=hpa@zytor.com \
--cc=kirill@shutemov.name \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mtosatti@redhat.com \
--cc=penberg@cs.helsinki.fi \
--cc=tglx@linutronix.de \
--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.