From: Andi Kleen <ak@suse.de>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
linux-stable <stable@kernel.org>
Subject: Re: [patch 2.6.17-rc3] i386: fix broken FP exception handling
Date: Sun, 30 Apr 2006 10:42:59 +0200 [thread overview]
Message-ID: <200604301042.59884.ak@suse.de> (raw)
In-Reply-To: <200604291409_MC3-1-BE50-16AD@compuserve.com>
On Saturday 29 April 2006 20:07, Chuck Ebbert wrote:
> The FXSAVE information leak patch introduced a bug in FP exception
> handling: it clears FP exceptions only when there are already
> none outstanding. Mikael Pettersson reported that causes problems
> with the Erlang runtime and has tested this fix.
Patch looks correct, thanks. All other cases (x86-64, 2.4) should
be already ok.
-Andi
next prev parent reply other threads:[~2006-04-30 8:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-29 18:07 [patch 2.6.17-rc3] i386: fix broken FP exception handling Chuck Ebbert
2006-04-30 8:42 ` Andi Kleen [this message]
2006-05-01 20:35 ` [stable] " Greg KH
-- strict thread matches above, loose matches on Subject: below --
2006-04-29 18:39 Mikael Pettersson
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=200604301042.59884.ak@suse.de \
--to=ak@suse.de \
--cc=76306.1226@compuserve.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=torvalds@osdl.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