linux-um archives
 help / color / mirror / Atom feed
From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: Matt Zimmerman <mdz@debian.org>,
	user-mode-linux-devel@lists.sourceforge.net
Cc: Marius Gedminas <mgedmin@b4net.lt>, 256873-forwarded@bugs.debian.org
Subject: Re: [uml-devel] [mgedmin@b4net.lt: Bug#256873: user-mode-linux: fails to start (kernel panic)]
Date: Tue, 29 Jun 2004 21:06:22 +0200	[thread overview]
Message-ID: <200406292106.22260.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <20040629182711.GM5243@alcor.net>

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

Alle 20:27, martedì 29 giugno 2004, Matt Zimmerman ha scritto:
> I am receiving many reports from my users that 2.4.26-1um is less
> functional than past versions, especially (but not exclusively) where
> hostfs is concerned.  Are others experiencing problems as well?  I am
> considering reverting the Debian packages to 2.4.24-1um, which was the last
> version which was stable for me (it had only one frustrating hostfs bug,
> where readdir() would read forever).

I definitely agree. There are some bugfix from 2.4.24-2 to add there, but they 
can wait for now (they are far less fatal). Also, the attached patch is 
needed as forward-port to 2.4.26: use vanilla 2.4.26+ 2.4.24-1um + the 
attached fixlet. Don't downgrade to the security-bugged 2.4.24/.25.

Bye
-- 
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729

[-- Attachment #2: uml-2.4.26-cmpxchg.patch --]
[-- Type: text/x-diff, Size: 1049 bytes --]

--- linux-2.4.26/include/asm-um/system-i386.h	Wed Apr 21 15:33:45 2004
+++ linux-2.4.26-umlfix/include/asm-um/system-i386.h	Wed Apr 21 15:27:14 2004
@@ -5,35 +5,4 @@
 
 #define __HAVE_ARCH_CMPXCHG 1
 
-static inline unsigned long __cmpxchg(volatile void *ptr, unsigned long old,
-				      unsigned long new, int size)
-{
-	unsigned long prev;
-	switch (size) {
-	case 1:
-		__asm__ __volatile__(LOCK_PREFIX "cmpxchgb %b1,%2"
-				     : "=a"(prev)
-				     : "q"(new), "m"(*__xg(ptr)), "0"(old)
-				     : "memory");
-		return prev;
-	case 2:
-		__asm__ __volatile__(LOCK_PREFIX "cmpxchgw %w1,%2"
-				     : "=a"(prev)
-				     : "q"(new), "m"(*__xg(ptr)), "0"(old)
-				     : "memory");
-		return prev;
-	case 4:
-		__asm__ __volatile__(LOCK_PREFIX "cmpxchgl %1,%2"
-				     : "=a"(prev)
-				     : "q"(new), "m"(*__xg(ptr)), "0"(old)
-				     : "memory");
-		return prev;
-	}
-	return old;
-}
-
-#define cmpxchg(ptr,o,n)\
-	((__typeof__(*(ptr)))__cmpxchg((ptr),(unsigned long)(o),\
-					(unsigned long)(n),sizeof(*(ptr))))
-    
 #endif

  reply	other threads:[~2004-06-29 18:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-29 18:27 [uml-devel] [mgedmin@b4net.lt: Bug#256873: user-mode-linux: fails to start (kernel panic)] Matt Zimmerman
2004-06-29 19:06 ` BlaisorBlade [this message]
2004-06-29 20:34 ` Stefan Gybas
2004-06-29 23:55 ` James Neal
2004-06-30  7:56   ` Paul Wagland
2004-06-30 18:38     ` BlaisorBlade
2004-07-01 21:02       ` Paul Wagland
2004-07-03 17:21         ` BlaisorBlade

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=200406292106.22260.blaisorblade_spam@yahoo.it \
    --to=blaisorblade_spam@yahoo.it \
    --cc=256873-forwarded@bugs.debian.org \
    --cc=mdz@debian.org \
    --cc=mgedmin@b4net.lt \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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