Ignore SIGURG about kmod-dblock HOT 3 CLOSED

okay, I can do that. gimme a bit.

from kmod-dblock.

okay give this a try.

there's two sides to the kernel module, and I ignore SIGURGs on the side that userspace is calling, so hopefully that will cover the cases you're running into.
lemme know if something else comes up.
I treat all signals as problems, so other things may come up like this.
I forget, but I think the signal is sent back to userspace, not sure.
if not, you can see if the return code is -EINTR and if so, just go back and call dblock_operation_block_for_request again.
but better to not bounce back and forth between userspace and kernel for no reason, it will just slow things down.

but there are signals I do want to get back to userspace, so I don't want to filter everything by default.

anyway, give this a go.
ha ha. go.

from kmod-dblock.

My test is passing cleanly this morning after this change. I also updated to retry on EINTR so legit interrupts should be handled gracefully. Thanks for the ultra quick turnaround 😄

from kmod-dblock.