From: Kasper Dupont <kasperd@daimi.au.dk>
To: Stas Sergeev <stssppnn@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] vm86 bugs in 2.5.30
Date: Sat, 10 Aug 2002 22:10:14 +0200 [thread overview]
Message-ID: <3D557326.CBD0E21E@daimi.au.dk> (raw)
In-Reply-To: 3D556EF1.5010708@yahoo.com
Stas Sergeev wrote:
>
> Hello.
>
> Kasper Dupont wrote:
> > <4> invalid operand: 0000
> > <4>Code: Bad EIP value.
> > It happens during the vm86 system call, but it is not fixed
> > by any of the changes in vm86.c. Who remember which patch
> > fixed this problem?
> This one:
> http://dosemu.sourceforge.net/stas/traps.diff
> Was not included in 2.4.19, exists only in -ac
> for now.
Thanks. I'm actually using -ac kernels. The reason I missed
this patch was that the change was in another file. Tomorrow
I'll try this against 2.5.30.
--
Kasper Dupont -- der bruger for meget tid på usenet.
For sending spam use mailto:razrep@daimi.au.dk
or mailto:mcxumhvenwblvtl@skrammel.yaboo.dk
next prev parent reply other threads:[~2002-08-10 20:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-10 19:52 [RFC] vm86 bugs in 2.5.30 Stas Sergeev
2002-08-10 20:10 ` Kasper Dupont [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-10 8:49 Kasper Dupont
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=3D557326.CBD0E21E@daimi.au.dk \
--to=kasperd@daimi.au.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=stssppnn@yahoo.com \
/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