Kevin Lawton wrote:
> So, we have to rehash code in kernel/emulation.c
> to always check ranges of guest memory, to see if
> they are accessible or not. If not, we have to
> redirect back to the host. Kind of like a verify_area()
> in Linux. No big deal, just have to have a good
> habit of verifying address ranges before examining the
> data.
Of course. That's why I've tried to encapsulate all access
to guest memory into routines (read/write_guest_dword etc.).
The page-present check should need to be added only there ...
(While we're at it, we might also fix the code to actually
respect guest segment registers ;-/ Then again, maybe that's
not a priority for now ...)
Bye,
Ulrich
--
Dr. Ulrich Weigand
[EMAIL PROTECTED]
