> So, in practice, it's correct to call bad_segv() as done in the patch, but we
> miss some cases. Only this time I've verified this well enough that I feel we
> could merge your patch. However, I've not found any possible *realistic*
> source of general protection faults. Especially I didn't find what expected
> (i.e. I/O errors).
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 ...
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
