> >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
[email protected]
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
