Hello Jeff,
this test is unnecessary since kfree() already handles NULL
I agree and normally kfree behaves in that way, but in this case the warning comes from free_large_kmalloc. Unbinding from VMs, the warning is always happening if the previous crash is fixed (first commit of this series).
Thanks
Best regards José Ignacio