Bug#1005900: linux.uml: uml_mconsole client becomes blocked on read after issuing commands stop and go

Hi Ritesh, hi Mihai, Apologies for the delay in the answer, I was traveling last week. 1. Your patch will not achieve the desired aim. The IRQS in UML nowadays are per fd and looping inside the IRQ handler for mconsole will not stop UML as it used to when it was using the old poll() based IRQ

Bug#1005900: linux.uml: uml_mconsole client becomes blocked on read after issuing commands stop and go

Hello Mihai, In this case, it is good to have the User Mode Linux upstream in the loop. Thanks, Ritesh --- linux-source-5.16/arch/um/drivers/mconsole_kern.c 2022-02-05 20:22:06.0 +0200 +++ linux-source-5.16.fix/arch/um/drivers/mconsole_kern.c 2022-02-16 23:35:39.562668086

Bug#1005900: linux.uml: uml_mconsole client becomes blocked on read after issuing commands stop and go

I failed to mention that the block on read occurs by sending anything through uml_mconsole, after the go command has been processed.

Bug#1005900: linux.uml: uml_mconsole client becomes blocked on read after issuing commands stop and go

Package: user-mode-linux Version: 5.16um1 Severity: normal File: /usr/bin/linux.uml X-Debbugs-Cc: quake2i...@gmail.com Dear Maintainer, * What is the problem: Issuing the commands stop followed by go, at the input of the uml_mconsole client, results in the client becoming blocked on read socket.