From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net,
Bodo Stroesser <bstroesser@fujitsu-siemens.com>,
user-mode-linux-user@lists.sourceforge.net
Cc: Gerd Knorr <kraxel@bytesex.org>,
Michael Richardson <mcr@sandelman.ottawa.on.ca>,
Henrik Nordstrom <hno@marasystems.com>,
"Christopher S. Aker" <caker@theshore.net>
Subject: [uml-devel] SKAS-v8: RC5 released against 2.6.7 - 2.6.11 kernels
Date: Fri, 11 Mar 2005 20:13:19 +0100 [thread overview]
Message-ID: <200503112013.20206.blaisorblade@yahoo.it> (raw)
This time, I've announced this on my homepage, since I'd like to get a lot
more testing and to release this patch unchanged as -V8 final version.
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. This will be done in -V9.
The summary of changes against -RC2 is short... I dropped
fix-dumpable-handling because I don't feel it secure yet, so everybody using
-RC2 should upgrade.
The problem is that the correct locking is difficult and even mainline kernel
code has a lot of confusion about it, and I want to sort this out first, to
avoid problems with the patch.
Sorry Michael, but this is lower priority than stability and security. It will
be for next patch.
Description of this patch.
* 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.
--
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-03-11 19:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-11 19:13 Blaisorblade [this message]
[not found] ` <200504142311.43374.blaisorblade@yahoo.it>
[not found] ` <1113928612.5221.10.camel@powerful.admindu.de>
2005-04-20 20:03 ` [uml-devel] Re: [uml-user] Loadav always >1.0 (2.6.X) 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=200503112013.20206.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=bstroesser@fujitsu-siemens.com \
--cc=caker@theshore.net \
--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