While it shouldn't happen on regular guests, we sometimes hit it when fuzzing within the guest, which would cause the lkvm process to exit - which is undesired.
Signed-off-by: Sasha Levin <[email protected]> --- tools/kvm/x86/ioport.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/kvm/x86/ioport.c b/tools/kvm/x86/ioport.c index 4993f9d..e35d0ee 100644 --- a/tools/kvm/x86/ioport.c +++ b/tools/kvm/x86/ioport.c @@ -5,7 +5,7 @@ static bool debug_io_out(struct ioport *ioport, struct kvm *kvm, u16 port, void *data, int size) { - exit(EXIT_SUCCESS); + return 0; } static struct ioport_operations debug_ops = { -- 1.7.12 -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
