Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Matthew Auld <matthew.auld@intel.com>, intel-xe@lists.freedesktop.org
Cc: Matthew Brost <matthew.brost@intel.com>
Subject: Re: [PATCH] drm/xe/userptr: Fix an incorrect assert
Date: Fri, 07 Mar 2025 15:57:23 +0100	[thread overview]
Message-ID: <34c2677bbb16a9863b5209a73d9d34daab13dc45.camel@linux.intel.com> (raw)
In-Reply-To: <e9513f16-1470-437f-8472-b73859ff88f2@intel.com>

On Fri, 2025-03-07 at 13:19 +0000, Matthew Auld wrote:
> On 07/03/2025 10:01, Thomas Hellström wrote:
> > The assert incorrectly checks the total length processed which
> > can in fact be greater than the number of pages. Fix.
> > 
> > Fixes: 0a98219bcc96 ("drm/xe/hmm: Don't dereference struct page
> > pointers without notifier lock")
> > Cc: Matthew Auld <matthew.auld@intel.com>
> > Cc: Matthew Brost <matthew.brost@intel.com>
> > Signed-off-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> Reviewed-by: Matthew Auld <matthew.auld@intel.com>
> 

Thanks for reviewing, Matt.
/Thomas


  reply	other threads:[~2025-03-07 14:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-07 10:01 [PATCH] drm/xe/userptr: Fix an incorrect assert Thomas Hellström
2025-03-07 10:07 ` ✓ CI.Patch_applied: success for " Patchwork
2025-03-07 10:07 ` ✓ CI.checkpatch: " Patchwork
2025-03-07 10:09 ` ✓ CI.KUnit: " Patchwork
2025-03-07 10:38 ` ✓ CI.Build: " Patchwork
2025-03-07 10:40 ` ✓ CI.Hooks: " Patchwork
2025-03-07 10:42 ` ✓ CI.checksparse: " Patchwork
2025-03-07 11:02 ` ✓ Xe.CI.BAT: " Patchwork
2025-03-07 13:19 ` [PATCH] " Matthew Auld
2025-03-07 14:57   ` Thomas Hellström [this message]
2025-03-08  2:09 ` ✗ Xe.CI.Full: failure for " Patchwork
2025-03-08 11:16   ` Thomas Hellström

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=34c2677bbb16a9863b5209a73d9d34daab13dc45.camel@linux.intel.com \
    --to=thomas.hellstrom@linux.intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --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