All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: "Christian König" <christian.koenig@amd.com>,
	intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [RFC PATCH] drm/ttm: Fix swapping dereferences of freed memory
Date: Thu, 27 May 2021 17:05:06 +0200	[thread overview]
Message-ID: <e594a1d45b22e92e052d1070beadc5928e5c0ba1.camel@linux.intel.com> (raw)
In-Reply-To: <8b3382726763050334a6cb214f7ba560eebf8f28.camel@linux.intel.com>

On Thu, 2021-05-27 at 17:01 +0200, Thomas Hellström wrote:
> On Thu, 2021-05-27 at 16:54 +0200, Christian König wrote:
> > Am 27.05.21 um 16:19 schrieb Thomas Hellström:
> > > The swapping code was dereference bo->ttm pointers without having
> > > the
> > > dma-resv lock held. Also it might try to swap out unpopulated
> > > bos.
> > > 
> > > Fix this by moving the bo->ttm dereference until we have the
> > > reservation
> > > lock. Check that the ttm_tt is populated after the swap_notify
> > > callback.
> > > 
> > > Signed-off-by: Thomas Hellström
> > > <thomas.hellstrom@linux.intel.com>
> > > ---
> > >   drivers/gpu/drm/ttm/ttm_bo.c     | 16 +++++++++++++++-
> > >   drivers/gpu/drm/ttm/ttm_device.c |  8 +++-----
> > >   2 files changed, 18 insertions(+), 6 deletions(-)
> > > 
> > > diff --git a/drivers/gpu/drm/ttm/ttm_bo.c
> > > b/drivers/gpu/drm/ttm/ttm_bo.c
> > > index 9f53506a82fc..86213d37657b 100644
> > > --- a/drivers/gpu/drm/ttm/ttm_bo.c
> > > +++ b/drivers/gpu/drm/ttm/ttm_bo.c
> > > @@ -1163,6 +1163,16 @@ int ttm_bo_swapout(struct
> > > ttm_buffer_object
> > > *bo, struct ttm_operation_ctx *ctx,
> > >         if (!ttm_bo_evict_swapout_allowable(bo, ctx, &place,
> > > &locked, NULL))
> > >                 return -EBUSY;
> > >   
> > > +       dma_resv_assert_held(bo->base.resv);
> > > +
> > > +       if (!bo->ttm ||
> > > +           bo->ttm->page_flags & TTM_PAGE_FLAG_SG ||
> > > +           bo->ttm->page_flags & TTM_PAGE_FLAG_SWAPPED) {
> > > +               if (locked)
> > > +                       dma_resv_unlock(bo->base.resv);
> > > +               return -EBUSY;
> > > +       }
> > > +
> > >         if (!ttm_bo_get_unless_zero(bo)) {
> > >                 if (locked)
> > >                         dma_resv_unlock(bo->base.resv);
> > > @@ -1215,7 +1225,8 @@ int ttm_bo_swapout(struct ttm_buffer_object
> > > *bo, struct ttm_operation_ctx *ctx,
> > >         if (bo->bdev->funcs->swap_notify)
> > >                 bo->bdev->funcs->swap_notify(bo);
> > >   
> > > -       ret = ttm_tt_swapout(bo->bdev, bo->ttm, gfp_flags);
> > > +       if (ttm_tt_is_populated(bo->ttm))
> > > +               ret = ttm_tt_swapout(bo->bdev, bo->ttm,
> > > gfp_flags);
> > 
> > Exactly that is what I won't recommend. We would try to swap out
> > the 
> > same BO over and over again with that.
> 
> But we wouldn't since the BO is taken off the LRU and never re-added,
> 
> 
In fact, we'd probably might want to take the !bo->ttm bos off the LRU
as well..

/Thomas

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

WARNING: multiple messages have this Message-ID (diff)
From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: "Christian König" <christian.koenig@amd.com>,
	intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [RFC PATCH] drm/ttm: Fix swapping dereferences of freed memory
Date: Thu, 27 May 2021 17:05:06 +0200	[thread overview]
Message-ID: <e594a1d45b22e92e052d1070beadc5928e5c0ba1.camel@linux.intel.com> (raw)
In-Reply-To: <8b3382726763050334a6cb214f7ba560eebf8f28.camel@linux.intel.com>

On Thu, 2021-05-27 at 17:01 +0200, Thomas Hellström wrote:
> On Thu, 2021-05-27 at 16:54 +0200, Christian König wrote:
> > Am 27.05.21 um 16:19 schrieb Thomas Hellström:
> > > The swapping code was dereference bo->ttm pointers without having
> > > the
> > > dma-resv lock held. Also it might try to swap out unpopulated
> > > bos.
> > > 
> > > Fix this by moving the bo->ttm dereference until we have the
> > > reservation
> > > lock. Check that the ttm_tt is populated after the swap_notify
> > > callback.
> > > 
> > > Signed-off-by: Thomas Hellström
> > > <thomas.hellstrom@linux.intel.com>
> > > ---
> > >   drivers/gpu/drm/ttm/ttm_bo.c     | 16 +++++++++++++++-
> > >   drivers/gpu/drm/ttm/ttm_device.c |  8 +++-----
> > >   2 files changed, 18 insertions(+), 6 deletions(-)
> > > 
> > > diff --git a/drivers/gpu/drm/ttm/ttm_bo.c
> > > b/drivers/gpu/drm/ttm/ttm_bo.c
> > > index 9f53506a82fc..86213d37657b 100644
> > > --- a/drivers/gpu/drm/ttm/ttm_bo.c
> > > +++ b/drivers/gpu/drm/ttm/ttm_bo.c
> > > @@ -1163,6 +1163,16 @@ int ttm_bo_swapout(struct
> > > ttm_buffer_object
> > > *bo, struct ttm_operation_ctx *ctx,
> > >         if (!ttm_bo_evict_swapout_allowable(bo, ctx, &place,
> > > &locked, NULL))
> > >                 return -EBUSY;
> > >   
> > > +       dma_resv_assert_held(bo->base.resv);
> > > +
> > > +       if (!bo->ttm ||
> > > +           bo->ttm->page_flags & TTM_PAGE_FLAG_SG ||
> > > +           bo->ttm->page_flags & TTM_PAGE_FLAG_SWAPPED) {
> > > +               if (locked)
> > > +                       dma_resv_unlock(bo->base.resv);
> > > +               return -EBUSY;
> > > +       }
> > > +
> > >         if (!ttm_bo_get_unless_zero(bo)) {
> > >                 if (locked)
> > >                         dma_resv_unlock(bo->base.resv);
> > > @@ -1215,7 +1225,8 @@ int ttm_bo_swapout(struct ttm_buffer_object
> > > *bo, struct ttm_operation_ctx *ctx,
> > >         if (bo->bdev->funcs->swap_notify)
> > >                 bo->bdev->funcs->swap_notify(bo);
> > >   
> > > -       ret = ttm_tt_swapout(bo->bdev, bo->ttm, gfp_flags);
> > > +       if (ttm_tt_is_populated(bo->ttm))
> > > +               ret = ttm_tt_swapout(bo->bdev, bo->ttm,
> > > gfp_flags);
> > 
> > Exactly that is what I won't recommend. We would try to swap out
> > the 
> > same BO over and over again with that.
> 
> But we wouldn't since the BO is taken off the LRU and never re-added,
> 
> 
In fact, we'd probably might want to take the !bo->ttm bos off the LRU
as well..

/Thomas


  reply	other threads:[~2021-05-27 15:05 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-27 14:19 [Intel-gfx] [RFC PATCH] drm/ttm: Fix swapping dereferences of freed memory Thomas Hellström
2021-05-27 14:19 ` Thomas Hellström
2021-05-27 14:54 ` [Intel-gfx] " Christian König
2021-05-27 14:54   ` Christian König
2021-05-27 15:01   ` [Intel-gfx] " Thomas Hellström
2021-05-27 15:01     ` Thomas Hellström
2021-05-27 15:05     ` Thomas Hellström [this message]
2021-05-27 15:05       ` Thomas Hellström
2021-05-27 15:32       ` [Intel-gfx] " Christian König
2021-05-27 15:32         ` Christian König
2021-05-27 15:51         ` [Intel-gfx] " Thomas Hellström
2021-05-27 15:51           ` Thomas Hellström
2021-05-28  7:16           ` [Intel-gfx] " Christian König
2021-05-28  7:16             ` Christian König
2021-05-28  7:33             ` [Intel-gfx] " Thomas Hellström
2021-05-28  7:33               ` Thomas Hellström
2021-05-28 14:10               ` [Intel-gfx] " Christian König
2021-05-28 14:10                 ` Christian König
2021-05-28 14:17                 ` [Intel-gfx] " Thomas Hellström
2021-05-28 14:17                   ` Thomas Hellström
2021-05-28 14:21                   ` [Intel-gfx] " Christian König
2021-05-28 14:21                     ` Christian König
2021-05-27 15:17     ` [Intel-gfx] " Christian König
2021-05-27 15:17       ` Christian König
2021-05-27 19:58 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for " 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=e594a1d45b22e92e052d1070beadc5928e5c0ba1.camel@linux.intel.com \
    --to=thomas.hellstrom@linux.intel.com \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.