From: fei.yang@intel.com
To: intel-xe@lists.freedesktop.org
Cc: matthew.d.roper@intel.com, lucas.demarchi@intel.com
Subject: [Intel-xe] [PATCH 0/1] drm/xe: timeout needs to be a signed value
Date: Mon, 25 Sep 2023 21:12:58 -0700 [thread overview]
Message-ID: <20230926041259.1102823-1-fei.yang@intel.com> (raw)
From: Fei Yang <fei.yang@intel.com>
In xe_wait_user_fence_ioctl, the timeout is currently defined as
unsigned long. That could potentially pass a negative value to
the schedule_timeout() call because nsecs_to_jiffies() returns an
unsigned long which gets used as signed long.
Signed-off-by: Fei Yang <fei.yang@intel.com>
Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>
Cc: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com>
Fei Yang (1):
drm/xe: timeout needs to be a signed value
drivers/gpu/drm/xe/xe_wait_user_fence.c | 55 +++++++++++++++++--------
1 file changed, 37 insertions(+), 18 deletions(-)
--
2.25.1
next reply other threads:[~2023-09-26 4:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 4:12 fei.yang [this message]
2023-09-26 4:12 ` [Intel-xe] [PATCH 1/1] drm/xe: timeout needs to be a signed value fei.yang
2023-09-26 8:25 ` Upadhyay, Tejas
2023-09-26 4:13 ` [Intel-xe] ✓ CI.Patch_applied: success for " Patchwork
2023-09-26 4:13 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-09-26 4:14 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-09-26 4:21 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-09-26 4:22 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-09-26 4:23 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-09-26 4:57 ` [Intel-xe] ✓ CI.BAT: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2023-09-21 22:04 [Intel-xe] [PATCH 0/1] " fei.yang
2023-09-29 6:04 ` Lucas De Marchi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230926041259.1102823-1-fei.yang@intel.com \
--to=fei.yang@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=matthew.d.roper@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox