linux-um archives
 help / color / mirror / Atom feed
From: Bodo Stroesser <bstroesser@fujitsu-siemens.com>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net,
	Rob Landley <rob@landley.net>
Subject: Re: [uml-devel] Am I doing something wrong with -skas0?
Date: Fri, 15 Jul 2005 18:25:18 +0200	[thread overview]
Message-ID: <42D7E36E.1060605@fujitsu-siemens.com> (raw)
In-Reply-To: <200507151810.39548.blaisorblade@yahoo.it>

Blaisorblade wrote:
> On Thursday 14 July 2005 22:30, Rob Landley wrote:
> 
>>On Thursday 14 July 2005 13:16, Rob Landley wrote:
>>
>>>Bodo's patch seems to have fixed the problem (albeit in a way that
>>>reveals ubuntu is using thread-local storage, so I can't use it anyway).
>>
>>Hang on a sec, if TLS is screwing up -skas0, then why does -tt mode work?
>>
>>Is this expected?
> 
> Hmm, I've seen TLS falling back on modify_ldt() at times, and it's surely a 
> bit bogus in current trees (although I have a partial fix for it, but not 
> sure whether it will work). Do you think init=/usr/bin/strace /bin/ls would 
> work? Uncomprehensible kernel params are passed to init, so it could.
Testing SKAS0 some month ago, I had problems with TLS in LDT, too. It didn't
print any message, but the processes looped on a segfault.
Debugging this, I changed SKAS0 to use the full faultinfo, so in the newer
versions it detects that the fault isn't fixable and generates SIGSEGV.
But I also had to add some code to make sys_modify_ldt work in SKAS0 (reading
and writing).

Most of this is in skas-hold-own-ldt, but further patches (e.g. skas0-clone)
might be necessary. The patches can be found in Jeff's incrementals.

	Bodo


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&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

  reply	other threads:[~2005-07-15 16:25 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-13  4:46 [uml-devel] Am I doing something wrong with -skas0? Rob Landley
2005-07-13 12:11 ` Bodo Stroesser
2005-07-13 21:47   ` Rob Landley
2005-07-14 10:59     ` Bodo Stroesser
2005-07-14 12:05       ` Bodo Stroesser
2005-07-14 13:43         ` Jeff Dike
2005-07-14 14:11           ` Bodo Stroesser
2005-07-14 14:23             ` Jeff Dike
2005-07-14 18:19               ` Rob Landley
2005-07-14 14:13           ` Bodo Stroesser
2005-07-14 18:02         ` Rob Landley
2005-07-14 13:40       ` Jeff Dike
2005-07-14 17:58       ` Rob Landley
2005-07-13 21:51   ` Rob Landley
2005-07-13 12:15 ` Jeff Dike
2005-07-13 21:56   ` Rob Landley
2005-07-13 23:29     ` Jeff Dike
2005-07-14  2:02       ` Rob Landley
2005-07-14 12:37         ` Jeff Dike
2005-07-14 18:16           ` Rob Landley
2005-07-14 20:30             ` Rob Landley
2005-07-15 16:10               ` Blaisorblade
2005-07-15 16:25                 ` Bodo Stroesser [this message]
2005-07-15 19:40                 ` Rob Landley

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=42D7E36E.1060605@fujitsu-siemens.com \
    --to=bstroesser@fujitsu-siemens.com \
    --cc=blaisorblade@yahoo.it \
    --cc=rob@landley.net \
    --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