From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net,
Bodo Stroesser <bstroesser@fujitsu-siemens.com>
Cc: user-mode-linux-user@lists.sourceforge.net,
Gerd Knorr <kraxel@bytesex.org>,
Michael Richardson <mcr@sandelman.ottawa.on.ca>,
Henrik Nordstrom <hno@marasystems.com>
Subject: [uml-devel] SKAS-v8: RC2 released against 2.6.7 - 2.6.11-rc3-bk6 kernels
Date: Fri, 11 Feb 2005 04:11:34 +0100 [thread overview]
Message-ID: <200502110411.35438.blaisorblade@yahoo.it> (raw)
This time, I've announced this on my homepage, since I'd like to get some more
testing.
Things I've forgot:
* make it apply easily on Fedora kernels.
This should simply mean moving the TIF_SYSCALL_EMU to place no.8, to leave a
slot free for _DB7, needed for 4g4g or something like that and using testw
instead of testb for testing against it.
Summary of changes against -V7 (also put in the "ChangeLog" page):
* for kernels >=2.6.10, in the splitout, various patches were folded together.
* rename-modify-ldt-to-avoid-conflicts.patch: fix the reported ATI module
compile problem by renaming modify_ldt to __modify_ldt.
* ptrace_ldt-reload-smp-fix.patch: fix a SMP-host bug noticed by Bodo
Stroesser.
* skas-add-locking-for-mm-switch.patch: from me, add correct locking to
PTRACE_SWITCH_MM to avoid races. Someone please test with SMP hosts / with
spinlock debugging enabled, to check for any possible deadlock. I'll do this
in next days, too.
* skas-reorganize and skas-add-SYSEMU_SINGLESTEP: from Bodo Stroesser, they
add the SYSEMU_SINGLESTEP mode. For 2.6.9 and beyond, I've cleaned up a lot
the second one to ease porting to 2.6.10.
* sysaudit-singlestep-umlhost.patch: for host >= 2.6.9, it fixes a bad
interaction between syscall auditing and ptracing. A version of this must
also go in 2.6.11.
* fix-dumpable-handling.patch: this implemented a feature / bug fix requested
by Michael Richardson <mcr@sandelman.ottawa.on.ca>. I.e., with this, in
normal cases, UML *is* allowed to dump core and be seen inside /proc - (until
now it was treated as if it was a setuid process or one which changed UID /
GID). If I did any error, however, it could allow privilege escalation. Well,
I've thought a bit about this, however I'll think even more before putting it
into a release (I wrote this more than one month ago).
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
http://www.user-mode-linux.org/~blaisorblade
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next reply other threads:[~2005-02-11 3:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-11 3:11 Blaisorblade [this message]
2005-02-14 23:46 ` [uml-devel] SKAS-v8: RC2 released against 2.6.7 - 2.6.11-rc3-bk6 kernels Christopher S. Aker
2005-02-15 0:20 ` Christopher S. Aker
2005-02-15 6:22 ` Jeff Dike
2005-02-15 4:31 ` Christopher S. Aker
2005-02-15 15:23 ` Bodo Stroesser
2005-02-16 19:10 ` Blaisorblade
2005-02-21 19:41 ` Christopher S. Aker
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=200502110411.35438.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=bstroesser@fujitsu-siemens.com \
--cc=hno@marasystems.com \
--cc=kraxel@bytesex.org \
--cc=mcr@sandelman.ottawa.on.ca \
--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