On Mon, May 15, 2023 at 3:23 PM Mike Christie <michael.christie@xxxxxxxxxx> wrote: > > The vhost layer really doesn't want any signals and wants to work like kthreads > for that case. To make it really simple can we do something like this where it > separates user and io worker behavior where the major diff is how they handle > signals and exit. I also included a fix for the freeze case: I don't love the SIGKILL special case, but I also don't find this deeply offensive. So if this is what it takes, I'm ok with it. I wonder if we could make that special case simply check for "is SIGKILL blocked" instead? No normal case will cause that, and it means that a PF_USER_WORKER thread could decide per-thread what it wants to do wrt SIGKILL. Christian? And I guess we should Cc: Oleg too, since the signal parts are an area he's familiar with and has worked on.. Eric Biederman has already been on the list and has also been involved Oleg: see https://lore.kernel.org/lkml/122b597e-a5fa-daf7-27bb-6f04fa98d496@xxxxxxxxxx/ for the context here. Linus _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/virtualization
