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.
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
Get latest updates about Open Source Projects, Conferences and News.