drm/amdgpu: Allow kfd CRIU with no buffer objects

The kfd CRIU checkpoint ioctl would return an error if trying
to checkpoint a process with no kfd buffer objects.

This is a normal case and should not be an error.

Reviewed-by: Felix Kuehling <felix.kuehling@amd.com>
Signed-off-by: David Francis <David.Francis@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

diff --git a/drivers/gpu/drm/amd/amdkfd/kfd_chardev.c b/drivers/gpu/drm/amd/amdkfd/kfd_chardev.c
index 43115a3744694337204b9a1dbc7a769de7195833..8535a52a62cab7d0a9441de1a3c8c67a7c29351e 100644 (file)
--- a/drivers/gpu/drm/amd/amdkfd/kfd_chardev.c
+++ b/drivers/gpu/drm/amd/amdkfd/kfd_chardev.c
@@ -2571,8 +2571,8 @@ static int criu_restore(struct file *filep,
        pr_debug("CRIU restore (num_devices:%u num_bos:%u num_objects:%u priv_data_size:%llu)\n",
                 args->num_devices, args->num_bos, args->num_objects, args->priv_data_size);
 
-       if (!args->bos || !args->devices || !args->priv_data || !args->priv_data_size ||
-           !args->num_devices || !args->num_bos)
+       if ((args->num_bos > 0 && !args->bos) || !args->devices || !args->priv_data ||
+           !args->priv_data_size || !args->num_devices)
                return -EINVAL;
 
        mutex_lock(&p->mutex);