linux-um archives
 help / color / mirror / Atom feed
From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net,
	user-mode-linux-user@lists.sourceforge.net
Subject: [uml-devel] Fixing the 2.4 bugs - patches against 2.4.24-1um
Date: Thu, 1 Jul 2004 20:50:14 +0200	[thread overview]
Message-ID: <200407012050.14867.blaisorblade_spam@yahoo.it> (raw)

I've started working also on UML/2.4.

Today I've split the changes between 2.4.24-1um and 2.4.24-2um into several 
patches; the HUMFS ones are carefully split out, but I've separated even the 
others. Now I need testers. Lots of people cannot use UML patches later than 
2.4.24-1um, since they contain a lot of Hostfs bugs and some stability 
issues. Now, if you use just some patches, you'll avoid the bugs in the 
other.

You should apply surely the first 3 patches, IMHO; the other ones should not 
hurt; inside txt/ there is a description of them.

mini-changes.patch
  Various little changes which don't hurt.

use_setjmp_wrapper.patch
  Adds setjmp_wrapper and use it, to fix klogd bug.

use-gettimeofday.patch
  Replace rdtsc with gettimeofday.

remapper-fix.patch
  Fixes probably to the ubd-mmap code

SIG-fileHandle-changes.patch
  Cope with signals from various places.

exec-shield.patch
  Patch for exec-shield users (IMHO unsafe)

expand-os-for-HUMFS.patch
  Expands os_ layer, seems to be for HUMFS only.

HUMFS.patch
  Adds HUMFS support, but create problems for Hostfs


The actual patches can be found inside the patches/ subdir in the tarball, and 
the "series" file contains the order.
THEY ARE AGAINST 2.4.24-1uml. If you want to apply it onto 2.4.26, don't 
forget to include the following patch (just for 2.4.26): 
http://vs165141.v.sectoor.de/uml-2.4.26-cmpxchg.patch

But you should move the content of 2.4.24-2-inc-split/ folder into the root of 
the linux tree (i.e. under Uml-linux) and then run "pushpatch 30" after 
installing patch-scripts.

Here there is the tarball:
http://www.user-mode-linux.org/~blaisorblade/patches/2.4.24-2-inc-split.tar.bz2

Here you can download patch-scripts; to install them you must just expand the 
tarball into /usr/local/bin (or any folder you like; remember to update the 
path if needed).

http://www.zip.com.au/~akpm/linux/patches/patch-scripts-0.18/

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



-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

             reply	other threads:[~2004-07-01 18:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-01 18:50 BlaisorBlade [this message]
2004-07-07 20:51 ` [uml-devel] Fixing the 2.4 bugs - patches against 2.4.24-1um Frank Sorenson
2004-07-08 16:38   ` [uml-user] " BlaisorBlade
2004-07-09 19:55     ` Frank Sorenson
2004-07-13 19:34   ` Jeff Dike
2004-07-15 15:39     ` Frank Sorenson
2004-07-21 17:27 ` [uml-devel] Fixing the 2.4 bugs - patches against 2.4.24-1um - new ones 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=200407012050.14867.blaisorblade_spam@yahoo.it \
    --to=blaisorblade_spam@yahoo.it \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    --cc=user-mode-linux-user@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