From: Patrick McHardy <kaber@trash.net>
To: Ingo Molnar <mingo@elte.hu>
Cc: Suresh Siddha <suresh.b.siddha@intel.com>,
Vegard Nossum <vegard.nossum@gmail.com>,
Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>,
Chuck Ebbert <cebbert@redhat.com>,
x86@kernel.org
Subject: Re: 2.6.26-git: NULL pointer deref in __switch_to
Date: Sat, 14 Jun 2008 09:39:13 +0200 [thread overview]
Message-ID: <485375A1.5000805@trash.net> (raw)
In-Reply-To: <20080614062014.GA7340@elte.hu>
Ingo Molnar wrote:
> * Suresh Siddha <suresh.b.siddha@intel.com> wrote:
>
>
>> Somehow (as described below?) TS_USEDFPU is set but the fpu is not
>> allocated or freed.
>>
>> Please try the appended patch.
>>
>
> i've queued up your fix in tip/x86/urgent. (Git access coordinates:
> http://people.redhat.com/mingo/tip.git/README)
>
> i'm wondering why this problem was not hit more frequently. Does it need
> some special FPU use to trigger? Or does it need an exec() with the FPU
> stack still active? (normally the FPU stack is empty at exec() time)
I've recently started running three lguest instances on that machine,
maybe that has something to do with it.
next prev parent reply other threads:[~2008-06-14 7:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-13 17:42 2.6.26-git: NULL pointer deref in __switch_to Patrick McHardy
2008-06-13 18:24 ` Vegard Nossum
2008-06-13 22:47 ` Suresh Siddha
2008-06-14 6:20 ` Ingo Molnar
2008-06-14 7:39 ` Patrick McHardy [this message]
2008-06-16 11:06 ` Jens Axboe
2008-06-14 7:36 ` Patrick McHardy
2008-06-16 10:15 ` Simon Holm Thøgersen
2008-06-16 10:29 ` Patrick McHardy
2008-06-16 12:10 ` Patrick McHardy
2008-06-16 17:49 ` Suresh Siddha
2008-06-16 21:21 ` Simon Holm Thøgersen
2008-06-17 23:50 ` Suresh Siddha
2008-06-18 5:34 ` Rusty Russell
2008-06-18 6:23 ` Suresh Siddha
2008-06-18 12:19 ` Rusty Russell
2008-06-18 8:42 ` Patrick McHardy
2008-06-18 13:57 ` Simon Holm Thøgersen
2008-06-13 20:10 ` Rafael J. Wysocki
2008-06-14 7:33 ` Patrick McHardy
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=485375A1.5000805@trash.net \
--to=kaber@trash.net \
--cc=cebbert@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=suresh.b.siddha@intel.com \
--cc=vegard.nossum@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox