public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Jeff Dike <jdike@karaya.com>
Cc: linux-kernel@vger.kernel.org, user-mode-linux-user@lists.sourceforge.net
Subject: Re: user-mode port 0.58-2.4.18-36
Date: Sat, 6 Jul 2002 03:16:45 +0200	[thread overview]
Message-ID: <20020706011643.GD112@elf.ucw.cz> (raw)
In-Reply-To: <200207052250.RAA03199@ccure.karaya.com>

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?

  reply	other threads:[~2002-07-06 18:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-05 22:50 user-mode port 0.58-2.4.18-36 Jeff Dike
2002-07-06  1:16 ` Pavel Machek [this message]
2002-07-06 23:03   ` [uml-user] " Jeff Dike
2002-07-09  3:16     ` Pavel Machek
2002-07-09 16:42       ` Jeff Dike
2002-07-09 16:55       ` Jeff Dike
2002-07-09 17:05         ` Pavel Machek
2002-07-09 18:47           ` Jeff Dike

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=20020706011643.GD112@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=jdike@karaya.com \
    --cc=linux-kernel@vger.kernel.org \
    --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