All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stas Sergeev <stsp@aknet.ru>
To: "James B. Hiller" <jhiller@visi.net>
Cc: linux-msdos@vger.kernel.org
Subject: Re: infinite loop on startup
Date: Sun, 09 May 2004 13:35:02 +0400	[thread overview]
Message-ID: <409DFB46.5000106@aknet.ru> (raw)
In-Reply-To: <200405090408.i4948ngZ004951@bassett.home.org>

[-- Attachment #1: Type: text/plain, Size: 820 bytes --]


Hello.

James B. Hiller wrote:
> Please let me know if this looks like your issue, and if you need
> anything else.
Yes, from the log it looks exactly the
same problem I have observed.
And here is the fix:
http://www.uwsg.indiana.edu/hypermail/linux/kernel/0405.0/1242.html

It is SMP-unsafe though, so in case you
have an SMP box with preemption enabled,
you'd better wait till the next kernel
-pre release:
http://www.uwsg.indiana.edu/hypermail/linux/kernel/0405.0/1265.html

Or you can use the attached patch instead,
which does exactly what Linus said. But I
haven't tested that one due to a lack of an
SMP box handy.

The problem is that noone yet have audithed
the 2.6 kernel for dosemu-compatibility the
way it was done with 2.4. So using 2.6 with
dosemu is not recommended yet, but I already
started that work.

[-- Attachment #2: tss_iobtm1.diff --]
[-- Type: text/plain, Size: 508 bytes --]


--- linux/arch/i386/kernel/process.c	2004-04-14 09:41:14.000000000 +0400
+++ linux/arch/i386/kernel/process.c	2004-05-07 14:54:13.000000000 +0400
@@ -292,8 +292,12 @@
 
 	/* The process may have allocated an io port bitmap... nuke it. */
 	if (unlikely(NULL != tsk->thread.io_bitmap_ptr)) {
+		int cpu = get_cpu();
+		struct tss_struct *tss = init_tss + cpu;
 		kfree(tsk->thread.io_bitmap_ptr);
 		tsk->thread.io_bitmap_ptr = NULL;
+		tss->io_bitmap_base = INVALID_IO_BITMAP_OFFSET;
+		put_cpu();
 	}
 }
 

[-- Attachment #3: Type: text/plain, Size: 82 bytes --]


Scanned by evaluation version of Dr.Web antivirus Daemon 
http://drweb.ru/unix/


       reply	other threads:[~2004-05-09  9:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200405090408.i4948ngZ004951@bassett.home.org>
2004-05-09  9:35 ` Stas Sergeev [this message]
     [not found] <200405091537.i49Fb2uu001301@bassett.home.org>
2004-05-09 15:50 ` infinite loop on startup Stas Sergeev
2004-05-08  9:56 Stas Sergeev
2004-05-09  0:10 ` James B. Hiller
  -- strict thread matches above, loose matches on Subject: below --
2004-03-14 19:52 Infinite " James B. Hiller

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=409DFB46.5000106@aknet.ru \
    --to=stsp@aknet.ru \
    --cc=jhiller@visi.net \
    --cc=linux-msdos@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.