From: Gerd Knorr <kraxel@bytesex.org>
To: Bodo Stroesser <bstroesser@fujitsu-siemens.com>
Cc: Blaisorblade <blaisorblade@yahoo.it>,
Jeff Dike <jdike@addtoit.com>,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Re: uml-general-protection-fault even more kludgy but mergeable
Date: Tue, 17 May 2005 12:59:34 +0200 [thread overview]
Message-ID: <20050517105934.GD20584@bytesex> (raw)
In-Reply-To: <4289C66C.9000709@fujitsu-siemens.com>
> >The case I trapped into was an attempt to access I/O ports of a
> >process running inside the uml. The uml kernel then tried to
> >handle that as page fault, which didn't work very well ...
> Unfortunately, I can't find the previous mails about this. So, maybe I'm
> totally wrong. If so, please discard this mail.
Yes, was discussed quite some time ago, more than half a year
IIRC.
> Gerd, did you see the problem in SKAS3 on i386? If so, it would be nice to
> see what happens in SKAS0.
Not tested yet.
> I saw similar problems regarding bad LDT-descriptors. Processes using a bad
> descriptor loop on page_fault.
>
> The real fix for this is to add trap_no to the info, that is read from host
> by PTRACE_FAULTINFO. With this info, UML can distinguish between real page
> faults and other SIGSEGVs.
Yes, that conclusion we came to as well, the real fix would be
pass on trap_no. The patch mentioned in $subject is a band-aid
fix to deal with it a bit better without having the trap number.
> In SKAS0, UML already has the full info, as it retrieves the info from a
> sigcontext.
Then skas0 should do fine in theory ;)
Gerd
--
-mm seems unusually stable at present.
-- akpm about 2.6.12-rc3-mm3
-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7412&alloc_id=16344&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
prev parent reply other threads:[~2005-05-17 11:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-16 22:05 [uml-devel] uml-general-protection-fault even more kludgy but mergeable Blaisorblade
2005-05-17 10:03 ` [uml-devel] " Gerd Knorr
2005-05-17 10:24 ` Bodo Stroesser
2005-05-17 10:59 ` Gerd Knorr [this message]
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=20050517105934.GD20584@bytesex \
--to=kraxel@bytesex.org \
--cc=blaisorblade@yahoo.it \
--cc=bstroesser@fujitsu-siemens.com \
--cc=jdike@addtoit.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.