From: Nirmoy Das <nirmoy.das@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Nirmoy Das <nirmoy.das@intel.com>,
Francois Dugast <francois.dugast@intel.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Matthew Auld <matthew.auld@intel.com>,
Matthew Brost <matthew.brost@intel.com>
Subject: [PATCH 0/2] Improve ufence addr validation and error handling
Date: Tue, 15 Oct 2024 11:05:44 +0200 [thread overview]
Message-ID: <20241015090546.3082719-1-nirmoy.das@intel.com> (raw)
Resending https://patchwork.freedesktop.org/series/139887/ with
Test-with tag to validate we catch bogus addr from userspace early.
Test-with: 20241014141839.1618518-1-nirmoy.das@intel.com
Cc: Francois Dugast <francois.dugast@intel.com>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: Matthew Auld <matthew.auld@intel.com>
Cc: Matthew Brost <matthew.brost@intel.com>
Nirmoy Das (2):
drm/xe/ufence: Prefetch ufence addr to catch bogus address
drm/xe/ufence: Warn if mmget_not_zero() fails
drivers/gpu/drm/xe/xe_sync.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
--
2.46.0
next reply other threads:[~2024-10-15 9:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 9:05 Nirmoy Das [this message]
2024-10-15 9:05 ` [PATCH 1/2] drm/xe/ufence: Prefetch ufence addr to catch bogus address Nirmoy Das
2024-10-15 9:05 ` [PATCH 2/2] drm/xe/ufence: Warn if mmget_not_zero() fails Nirmoy Das
2024-10-15 12:48 ` Maarten Lankhorst
2024-10-15 12:59 ` Nirmoy Das
2024-10-15 12:46 ` ✓ CI.Patch_applied: success for Improve ufence addr validation and error handling Patchwork
2024-10-15 12:46 ` ✓ CI.checkpatch: " Patchwork
2024-10-15 12:48 ` ✓ CI.KUnit: " Patchwork
2024-10-15 12:59 ` ✓ CI.Build: " Patchwork
2024-10-15 13:01 ` ✓ CI.Hooks: " Patchwork
2024-10-15 13:03 ` ✓ CI.checksparse: " Patchwork
2024-10-15 21:14 ` ✗ CI.FULL: failure " Patchwork
2024-10-16 5:34 ` ✓ CI.Patch_applied: success for Improve ufence addr validation and error handling (rev2) Patchwork
2024-10-16 5:34 ` ✓ CI.checkpatch: " Patchwork
2024-10-16 5:35 ` ✓ CI.KUnit: " Patchwork
2024-10-16 5:47 ` ✓ CI.Build: " Patchwork
2024-10-16 5:49 ` ✓ CI.Hooks: " Patchwork
2024-10-16 5:51 ` ✓ CI.checksparse: " Patchwork
2024-10-16 6:15 ` ✓ CI.BAT: " Patchwork
2024-10-16 13:56 ` ✗ CI.FULL: failure " Patchwork
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=20241015090546.3082719-1-nirmoy.das@intel.com \
--to=nirmoy.das@intel.com \
--cc=francois.dugast@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matthew.auld@intel.com \
--cc=matthew.brost@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