On Mon, 2022-06-06 at 18:16 -0500, Glenn Washburn wrote:
> GDB says that the process was terminated with
> SIGKILL, which I'm guessing is why uml_console_exit() is not run.
>
https://patchwork.ozlabs.org/project/linux-um/patch/20220520194536.1acbb414a2d1.I1d71bab01d45f7f8e446df6e98547a7989338208
If VHOST_USER_PROTOCOL_F_INBAND_NOTIFICATIONS is activated, the user mode
linux virtio irq handler only read one msg from the corresponding socket.
This creates issues, when the device emulation creates multiple call
requests (e.g. for multiple virtqueues), as the socket buffer tend to fill
up and
Sorry for the cluttered HTML-Email, I hoped I trained my thunderbird to
do the right thing, but it didn't.
Am 07.06.2022 um 13:32 schrieb Benjamin Beichler:
Am 02.06.2022 um 10:32 schrieb Benjamin Beichler:
Am 01.06.2022 um 19:13 schrieb Johannes Berg:
prefer to keep the + on the previous lin
On Tue, 07 Jun 2022 10:22:43 +0200
Johannes Berg wrote:
> On Mon, 2022-06-06 at 18:16 -0500, Glenn Washburn wrote:
> > GDB says that the process was terminated with
> > SIGKILL, which I'm guessing is why uml_console_exit() is not run.
> >
>
> https://patchwork.ozlabs.org/project/linux-um/patch
On 06/06, Eric W. Biederman wrote:
>
> Which if I have had enough sleep reduces this patch to just:
>
> diff --git a/kernel/exit.c b/kernel/exit.c
> index f072959fcab7..c8156366b722 100644
> --- a/kernel/exit.c
> +++ b/kernel/exit.c
> @@ -1431,8 +1431,10 @@ static int child_wait_callback(wait_queue
On 06/06, Eric W. Biederman wrote:
>
> Oleg Nesterov writes:
>
> > However the patch looks fine to me, just the word "buggy" looks a bit
> > too strong imo.
>
> I guess I am in general agreement. Perhaps I can just say they values
> are wrong by definition?
Up to you. I won't really argue with "
From: Johannes Berg
[ Upstream commit d5a9597d6916a76663085db984cb8fe97f0a5c56 ]
Today, all possible serial lines (ssl*=) as well as all
possible consoles (con*=) each share a single interrupt
(with a fixed number) with others of the same type.
Now, if you have two lines, say ssl0 and ssl1, and
From: Johannes Berg
[ Upstream commit d5a9597d6916a76663085db984cb8fe97f0a5c56 ]
Today, all possible serial lines (ssl*=) as well as all
possible consoles (con*=) each share a single interrupt
(with a fixed number) with others of the same type.
Now, if you have two lines, say ssl0 and ssl1, and
From: Johannes Berg
[ Upstream commit d5a9597d6916a76663085db984cb8fe97f0a5c56 ]
Today, all possible serial lines (ssl*=) as well as all
possible consoles (con*=) each share a single interrupt
(with a fixed number) with others of the same type.
Now, if you have two lines, say ssl0 and ssl1, and
