Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Matthew Brost <matthew.brost@intel.com>
Cc: intel-xe@lists.freedesktop.org, matthew.auld@intel.com
Subject: Re: [PATCH v4 1/2] drm/xe: Userptr invalidation race with binds fixes
Date: Wed, 26 Feb 2025 16:13:49 +0100	[thread overview]
Message-ID: <a01fc6c3fb193574879f9d401accaa1385d32529.camel@linux.intel.com> (raw)
In-Reply-To: <Z74iu8n7Xe/mz6Uh@lstrano-desk.jf.intel.com>

On Tue, 2025-02-25 at 12:06 -0800, Matthew Brost wrote:
> On Tue, Feb 25, 2025 at 11:23:26AM -0800, Matthew Brost wrote:
> > On Tue, Feb 25, 2025 at 07:56:36PM +0100, Thomas Hellström wrote:
> > > On Tue, 2025-02-25 at 09:45 -0800, Matthew Brost wrote:
> > > > On Tue, Feb 25, 2025 at 03:30:54PM +0100, Thomas Hellström
> > > > wrote:
> > > > > Hi, Matt,
> > > > > 
> > > > > On Mon, 2025-02-24 at 09:01 -0800, Matthew Brost wrote:
> > > > > > Always wait on dma-resv bookkeep slots if userptr
> > > > > > invalidation
> > > > > > has
> > > > > > raced
> > > > > > with a bind ensuring PTEs temporally setup to invalidated
> > > > > > pages
> > > > > > are
> > > > > > never accessed.
> > > > > > 
> > > > > > Fixup initial bind handling always add VMAs to invalidation
> > > > > > list
> > > > > > and
> > > > > > wait dma-resv bookkeep slots.
> > > > > > 
> > > > > > Always hold notifier across TLB invalidation in notifier to
> > > > > > prevent a
> > > > > > UAF if an unbind races.
> > > > > > 
> > > > > > Including all of the above changes for Fixes patch in hopes
> > > > > > of an
> > > > > > easier
> > > > > > backport which fix a single patch.
> > > > > > 
> > > > > > v2:
> > > > > >  - Wait dma-resv bookkeep before issuing PTE zap (Thomas)
> > > > > >  - Support scratch page on invalidation (Thomas)
> > > > > > v3:
> > > > > >  - Drop clear of PTEs (Thomas)
> > > > > 
> > > > > This was what I actually meant.
> > > > > 
> > > > 
> > > > Ok, I presented this as option and it wasn't clear to me this
> > > > was
> > > > preferred.
> > > 
> > > Well, I think the more special cases we can get rid of in the
> > > code, the
> > 
> > Sure, not opposed this direction.
> > 
> > > better? Or at least, like in this case, split out what's common
> > > with
> > > the vm notifier into an xe_vm function and call that, making it
> > > more
> > > clear to the reader that we force an invalidation.
> > > 
> > > > 
> > > > > https://patchwork.freedesktop.org/patch/639489/?series=145409&rev=1
> > > > > 
> > > > 
> > > > This patch is doesn't work.
> > > > xe_vm.munmap-style-unbind-userptr-one-partial hangs due the
> > > > error
> > > > injection always firing on a single user bind, so we'd have to
> > > > fix
> > > > the
> > > > error injection too.
> > > 
> > > I have a follow up patch that splits out a part of the notifier
> > > like
> > > described above and calls that for each inject, also invalidating
> > > the
> > > userptr's seqno, and that fixes the above problem, but then the
> > > code
> > > hangs in 
> > > 
> > 
> > Ok, that sounds good.
> >  
> > > xe_exec_fault_mode --r once-userptr-prefetch
> > > 
> > > but that's a different failure mode. Apparently the prefetch code
> > > doesn't repin an invalid userptr and returns -EAGAIN forever...
> > > 
> > 
> > I see the issue, we only call xe_vma_userptr_pin_pages in new_vma
> > which
> > the prefetch code bypasses. If the error inject messes with userptr
> > seqno it makes sense this would start to show up. I suppose this
> > needs
> > fixing too.
> > 
> 
> Something like this shoud do the trick:
> 
> @@ -2299,8 +2299,16 @@ static int vm_bind_ioctl_ops_parse(struct
> xe_vm *vm, struct drm_gpuva_ops *ops,
>                         break;
>                 }
>                 case DRM_GPUVA_OP_UNMAP:
> +                       xe_vma_ops_incr_pt_update_ops(vops, op-
> >tile_mask);
> +                       break;
>                 case DRM_GPUVA_OP_PREFETCH:
> -                       /* FIXME: Need to skip some prefetch ops */
> +                       vma = gpuva_to_vma(op->base.prefetch.va);
> +
> +                       if (xe_vma_is_userptr(vma)) {
> +                               err = xe_vma_is_userptr(vma);
> +                               if (err)
> +                                       return err;
> +                       }
>                         xe_vma_ops_incr_pt_update_ops(vops, op-
> >tile_mask);
>                         break;
>                 default:
> 
> Matt
> 
> > Matt 

Yeah, I'll try to put something together based on this + your staging
tree patch.

/Thomas


  reply	other threads:[~2025-02-26 15:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-24 17:01 [PATCH v4 0/2] Userptr fixes Matthew Brost
2025-02-24 17:01 ` [PATCH v4 1/2] drm/xe: Userptr invalidation race with binds fixes Matthew Brost
2025-02-25 14:30   ` Thomas Hellström
2025-02-25 17:45     ` Matthew Brost
2025-02-25 18:56       ` Thomas Hellström
2025-02-25 19:23         ` Matthew Brost
2025-02-25 20:06           ` Matthew Brost
2025-02-26 15:13             ` Thomas Hellström [this message]
2025-02-24 17:01 ` [PATCH v4 2/2] drm/xe: Add staging tree for VM binds Matthew Brost
2025-02-25  0:17 ` ✓ CI.Patch_applied: success for Userptr fixes Patchwork
2025-02-25  0:17 ` ✓ CI.checkpatch: " Patchwork
2025-02-25  0:18 ` ✓ CI.KUnit: " Patchwork
2025-02-25  0:35 ` ✓ CI.Build: " Patchwork
2025-02-25  0:37 ` ✓ CI.Hooks: " Patchwork
2025-02-25  0:38 ` ✓ CI.checksparse: " Patchwork
2025-02-25  0:58 ` ✓ Xe.CI.BAT: " Patchwork
2025-02-25  3:53 ` ✗ Xe.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=a01fc6c3fb193574879f9d401accaa1385d32529.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