mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul <set@pobox.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [OOPS] repeatable 2.4.8-ac7, 2.4.7-ac6 [I] just run xdos
Date: Sun, 19 Aug 2001 21:43:22 -0400	[thread overview]
Message-ID: <20010819214322.D1315@squish.home.loc> (raw)
In-Reply-To: <Pine.LNX.4.33.0108191600580.10914-100000@boston.corp.fedex.com> <m166bjokre.fsf@frodo.biederman.org>
In-Reply-To: <m166bjokre.fsf@frodo.biederman.org>; from ebiederm@xmission.com on Sun, Aug 19, 2001 at 02:30:29PM -0600

"Eric W. Biederman" <ebiederm@xmission.com>, on Sun Aug 19, 2001 [02:30:29 PM] said:
[...]
> 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
> 
	Dear Eric;

	No, the program isnt setuid, nor run by root, and no
ports specified in the config. Let me know if there is anything
further I can do.

Paul
set@pobox.com


  reply	other threads:[~2001-08-20  1:44 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-19  4:47 [OOPS] repeatable 2.4.8-ac7, 2.4.7-ac6 " 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
2001-08-20  1:43         ` Paul [this message]
2001-08-20  6:09           ` [OOPS] repeatable 2.4.8-ac7, 2.4.7-ac6 [I] " 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

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=20010819214322.D1315@squish.home.loc \
    --to=set@pobox.com \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.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

all inboxes | Powered by JetHome®