From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] I'm out for some time - SKAS host leak diagnosis.
Date: Thu, 8 Jul 2004 18:04:40 +0200 [thread overview]
Message-ID: <200407081804.40148.blaisorblade_spam@yahoo.it> (raw)
1) From 9 to 18 July, I'll be away for study - so I won't be able to
participate in the UML development. Sadly, after coming back I'll be far away
from Internet, after a short time; however I think I'll be able to do
something before starting again (and while away I'll have my new laptop, so
I'll have plenty of time for coding).
2) Especially, I'm near to fixing the host SKAS leak... seems like it's a race
condition when calling alloc_ldt(): one of the two values is overwritten by
the other, and so never freed. In fact for each mm init_new_context() is
called when open()ing it, while __init_new_context() is called when writing a
MM_COPY_SEGMENTS request onto /proc/mm (which happens shortly after).
The mm->context is not locked anyway, and this is a SKAS bug: it makes sense
in mainline, but not when using SKAS. The strange thing is that on
host/kernel configurations where it happens, it is repeatable, i.e. does not
seem a race condition. However the locking must be anyway added.
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
next reply other threads:[~2004-07-08 16:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-08 16:04 BlaisorBlade [this message]
2004-07-19 17:58 ` I'm back - glibc LDT handling (was: Re: [uml-devel] I'm out for some time - SKAS host leak diagnosis.) BlaisorBlade
2004-07-19 18:45 ` 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=200407081804.40148.blaisorblade_spam@yahoo.it \
--to=blaisorblade_spam@yahoo.it \
--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