drm/amdkfd: Check bounds on CRIU restore event id

The valid amdkfd event ids go from 0 to KFD_SIGNAL_EVENT_LIMIT - 1.

During CRIU restore, ensure that the provided event ids are
in that range.

v2: No need for lower bound check since idr_alloc rejects negative
inputs

v3: Also change error message to reflect new error condition

Reviewed-by: David Yat Sin <david.yatsin@amd.com>
Signed-off-by: David Francis <David.Francis@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
(cherry picked from commit 5c6c247992d4d9200e073b83f4ec6c703c096845)

diff --git a/drivers/gpu/drm/amd/amdkfd/kfd_events.c b/drivers/gpu/drm/amd/amdkfd/kfd_events.c
index 81900b49d9d5b5a8d499d8f67afa8943bcebbe70..8cb43010ab1c78df41a0e9c76b4feb61de7d4ea5 100644 (file)
--- a/drivers/gpu/drm/amd/amdkfd/kfd_events.c
+++ b/drivers/gpu/drm/amd/amdkfd/kfd_events.c
@@ -204,7 +204,7 @@ static int create_signal_event(struct file *devkfd, struct kfd_process *p,
 
        ret = allocate_event_notification_slot(p, ev, restore_id);
        if (ret) {
-               pr_warn("Signal event wasn't created because out of kernel memory\n");
+               pr_warn("Failed to create signal event notification slot\n");
                return ret;
        }