Hi!
> This is the fourth release of the 2.4.18 UML.
>
> The major changes in this release include:
>
> It is now possible the to attach the UML gdb to sleeping threads.
> This is done by detaching gdb from the in-context thread and attaching
> it to the host pid of the sleeping UML process. UML may be continued
> by reattaching to the in-context thread. This feature was sponsored
> by Cluster File Systems, Inc.
>
> There is a /proc/exitcode, which allows a UML process to set the
> eventual UML exit code.
>
> Fixed some segfaults caused by calling openpty, which has an unusually
> large stack frame, overflowing the UML kernel stack.
>
> The tty logging patch is integrated. This allows UML honeypots to
> log all tty traffic to a host file. This logging can't be detected
> or interfered with by root inside the UML.
So... what prevents uml root from inserting rogue module (perhaps
using /dev/kmem) and escape the jail?
> The UML binary now lives in its own physical memory. This makes it
> easier for the swsusp patch to be ported to UML.
Good ;-).
Pavel
-- Worst form of spam? Adding advertisment signatures ala sourceforge.net. What goes next? Inserting advertisment *into* email? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Jul 07 2002 - 22:00:17 EST