From: Stas Sergeev <stsp@aknet.ru>
To: Jakob Eriksson <jakov@vmlinux.org>
Cc: Andi Kleen <ak@muc.de>, Pavel Machek <pavel@ucw.cz>,
Alan Cox <alan@redhat.com>,
Linux kernel <linux-kernel@vger.kernel.org>,
Petr Vandrovec <vandrove@vc.cvut.cz>,
Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>,
wine-devel@winehq.org, torvalds@osdl.org, the3dfxdude@gmail.com
Subject: Re: [patch] x86: fix ESP corruption CPU bug
Date: Mon, 14 Mar 2005 21:02:53 +0300 [thread overview]
Message-ID: <4235D1CD.1040304@aknet.ru> (raw)
In-Reply-To: <4235AC0B.70507@vmlinux.org>
Hi,
Jakob Eriksson wrote:
> A long term goal of wine is to support DOS apps to. Of course
> it's not a priority, but it's there.
Yes, that's exactly what I was hoping
for, thanks!
Even if no Windows apps do such a thing
(which wasn't confirmed yet), Wine may
still need that fix for the DOS support
in the future, and dosemu seems to be in
need of that fix already and for long
(that's where I am getting the use of it).
And we haven't heard a word for a VMWare
yet, and I think they may appreciate that
too.
Also, since the first version of the path,
I've been contacted by a few people asking
me to provide an updated version for 2.6.9
and 2.6.10. I don't know the reason, but
I know it was used (I think they were more
concerned about an aforementioned "information
leak", rather than about the %esp corruption).
So if the last problem with that patch was
that it is not really needed, I think it
no longer stays:)
next prev parent reply other threads:[~2005-03-14 18:06 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-13 18:20 [patch] x86: fix ESP corruption CPU bug Stas Sergeev
2005-03-13 18:52 ` Grzegorz Kulewski
2005-03-13 19:11 ` Stas Sergeev
2005-03-13 19:37 ` Ondrej Zary
2005-03-13 19:46 ` Stas Sergeev
2005-03-13 20:02 ` Pavel Machek
2005-03-13 20:10 ` Pavel Machek
2005-03-13 20:55 ` Stas Sergeev
2005-03-13 21:13 ` Linus Torvalds
2005-03-13 22:06 ` [patch] x86: fix ESP corruption CPU bug (take 2) Stas Sergeev
2005-03-14 19:29 ` Alan Cox
2005-03-14 19:59 ` Stas Sergeev
2005-03-15 3:34 ` Andrew Morton
2005-03-15 10:48 ` x86: spin_unlock(), spin_unlock_irq() & others are out of line ? Eric Dumazet
2005-03-15 19:44 ` Lee Revell
2005-03-15 19:48 ` [patch] x86: fix ESP corruption CPU bug (take 2) Stas Sergeev
2005-03-13 23:17 ` [patch] x86: fix ESP corruption CPU bug Pavel Machek
2005-03-13 23:54 ` Linus Torvalds
2005-03-14 0:16 ` Linus Torvalds
2005-03-14 4:52 ` Stas Sergeev
2005-03-14 9:34 ` Andi Kleen
2005-03-14 10:37 ` [BUG?] x86_64 : Can not read /dev/kmem ? Eric Dumazet
2005-03-21 19:37 ` Andi Kleen
2005-03-22 15:24 ` Andi Kleen
2005-03-14 15:21 ` [patch] x86: fix ESP corruption CPU bug Jakob Eriksson
2005-03-14 17:03 ` linux-os
2005-03-14 17:10 ` Pavel Machek
2005-03-14 19:24 ` Brian Gerst
2005-03-14 20:21 ` Stas Sergeev
2005-03-14 18:02 ` Stas Sergeev [this message]
2005-03-14 17:29 ` Stas Sergeev
-- strict thread matches above, loose matches on Subject: below --
2005-03-14 11:10 Zoltan Boszormenyi
2005-01-03 23:39 Stas Sergeev
2005-01-04 0:01 ` Linus Torvalds
2005-01-04 1:58 ` Stas Sergeev
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=4235D1CD.1040304@aknet.ru \
--to=stsp@aknet.ru \
--cc=ak@muc.de \
--cc=alan@redhat.com \
--cc=jakov@vmlinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=the3dfxdude@gmail.com \
--cc=torvalds@osdl.org \
--cc=vandrove@vc.cvut.cz \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
--cc=wine-devel@winehq.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