On 17.09.2019 18:04, Jan Beulich wrote: > On 17.09.2019 17:00, Alexandru Stefan ISAILA wrote: >> There is no problem, I understand the risk of having suspicious return >> values. I am not hanged on having this return. I used this to skip >> adding a new return value. I can do this if we agree on a suitable name >> for a new return value in enum hvm_translation_result. I can propose >> HVMTRANS_bad_gfn_access. > > How intrusive would such a change be? >
Only the return for hvm_copy_to_guest_linear() and hvm_copy_from_guest_linear() will be affected. There are 2 places to add checks, in linear_write() and linear_read(). The new return value can turn up only in hvm_emulate_one_vm_event() context, when vm_event->send_event flag is true. Alex _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
