public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Jeff Chua <jeffchua@silk.corp.fedex.com>
Cc: Paul <set@pobox.com>, Jeff Chua <jchua@fedex.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [OOPS] repeatable 2.4.8-ac7, 2.4.7-ac6 just run xdos
Date: 19 Aug 2001 14:30:29 -0600	[thread overview]
Message-ID: <m166bjokre.fsf@frodo.biederman.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0108191600580.10914-100000@boston.corp.fedex.com>
In-Reply-To: <Pine.LNX.4.33.0108191600580.10914-100000@boston.corp.fedex.com>

Jeff Chua <jeffchua@silk.corp.fedex.com> writes:

> On Sun, 19 Aug 2001, Paul wrote:
> > 	Actually, it works fine for me too, _if_ I use DOS 5 as
> > the boot image, but I changed to DOS 6.22, and its has oops'd
> > every time Ive tried it that way. Its just a trigger for whatever
> > the real problem is.
> >
> > Paul
> > set@pobox.com
> 
> I'm using dosemu-1.1.1.tgz with Windows 98 [Version 4.10.2222]
> 
> Does "dos" command works for you instead of "xdos" ?
> 
> Did you check your shmmax?
> 
> Try ...
> 	echo 1000000000 >/proc/sys/kernel/shmmax

This should be totally irrelevant.  You shouldn't be able to
crash linux with dosemu unless you are doing direct hardware access.

There are a number of cases, where dosemu is different enough it has
been known to cause code to go down buggy non-common paths and cause
things to fail.  This has happened with both X and the kernel.
I suspect that is what is happening here.

Paul is dosemu configured to do any direct hardware access?

Also of interest is that this crash is not even directly triggered by
the dosemu process.  Instead an interrupt handler is doing something
bad.  

Paul If you can verify that dosemu isn't doing any direct hardware
access.  i.e. Dosemu isn't suid root, and you have no ports lines
you should be fine.

Eric



  reply	other threads:[~2001-08-19 20:38 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-19  4:47 [OOPS] repeatable 2.4.8-ac7, 2.4.7-ac6 just run xdos Paul
2001-08-19  5:09 ` Jeff Chua
2001-08-19  5:40   ` Paul
2001-08-19  8:04     ` Jeff Chua
2001-08-19 20:30       ` Eric W. Biederman [this message]
2001-08-20  1:43         ` [OOPS] repeatable 2.4.8-ac7, 2.4.7-ac6 [I] " Paul
2001-08-20  6:09           ` Eric W. Biederman
2001-08-21  1:14             ` Paul
2001-08-21  6:08               ` Eric W. Biederman
2001-08-21 16:14                 ` Wilfried Weissmann
     [not found]                 ` <3B828898.BD98D4C4@gmx.at>
2001-08-21 16:20                   ` Eric W. Biederman
2001-08-21 18:49                     ` Wilfried Weissmann
2001-08-21 21:50                       ` Wilfried Weissmann
2001-08-22  1:42                 ` Paul
2001-08-22  7:56                   ` Eric W. Biederman
2001-08-19  5:10 ` [OOPS] repeatable 2.4.8-ac7, 2.4.7-ac6 " Jeff Chua
2001-08-22  2:45 ` Brian Gerst
     [not found]   ` <20010821232557.G218@squish.home.loc>
     [not found]     ` <3B832904.491AFE0E@didntduck.org>
2001-08-22  4:43       ` [OOPS] [resolution] Paul
     [not found] <20010819004703.A226@squish.home.loc.suse.lists.linux.kernel>
     [not found] ` <3B831CDF.4CC930A7@didntduck.org.suse.lists.linux.kernel>
2001-08-22 11:16   ` [OOPS] repeatable 2.4.8-ac7, 2.4.7-ac6 just run xdos Andi Kleen
2001-08-22 11:57     ` Brian Gerst
2001-08-22 12:10       ` Andi Kleen
2001-08-22 12:11         ` Brian Gerst
2001-08-22 13:22           ` Andi Kleen
2001-08-22 19:52             ` Paul
2001-08-23 13:34               ` Andi Kleen
2001-08-23 18:05                 ` Paul
2001-08-23 18:20                   ` Wayne Whitney

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=m166bjokre.fsf@frodo.biederman.org \
    --to=ebiederm@xmission.com \
    --cc=jchua@fedex.com \
    --cc=jeffchua@silk.corp.fedex.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=set@pobox.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