virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: "Christian König via Virtualization" <virtualization@lists.linux-foundation.org>
To: "Dmitry Osipenko" <dmitry.osipenko@collabora.com>,
	"David Airlie" <airlied@linux.ie>,
	"Gerd Hoffmann" <kraxel@redhat.com>,
	"Gurchetan Singh" <gurchetansingh@chromium.org>,
	"Chia-I Wu" <olvaffe@gmail.com>,
	"Daniel Vetter" <daniel@ffwll.ch>,
	"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
	"Maxime Ripard" <mripard@kernel.org>,
	"Thomas Zimmermann" <tzimmermann@suse.de>,
	"Emil Velikov" <emil.l.velikov@gmail.com>,
	"Thomas Hellström" <thomas_os@shipmail.org>
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	virtualization@lists.linux-foundation.org,
	linux-tegra@vger.kernel.org, Dmitry Osipenko <digetx@gmail.com>,
	kernel@collabora.com
Subject: Re: [PATCH v8 1/2] drm/gem: Properly annotate WW context on drm_gem_lock_reservations() error
Date: Tue, 5 Jul 2022 13:33:51 +0200	[thread overview]
Message-ID: <a42237c9-6304-4b06-cede-2175c7e7b87d@amd.com> (raw)
In-Reply-To: <20220701090240.1896131-2-dmitry.osipenko@collabora.com>

Am 01.07.22 um 11:02 schrieb Dmitry Osipenko:
> Use ww_acquire_fini() in the error code paths. Otherwise lockdep
> thinks that lock is held when lock's memory is freed after the
> drm_gem_lock_reservations() error. The ww_acquire_context needs to be
> annotated as "released", which fixes the noisy "WARNING: held lock freed!"
> splat of VirtIO-GPU driver with CONFIG_DEBUG_MUTEXES=y and enabled lockdep.
>
> Cc: stable@vger.kernel.org
> Fixes: 7edc3e3b975b5 ("drm: Add helpers for locking an array of BO reservations.")
> Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> Signed-off-by: Dmitry Osipenko <dmitry.osipenko@collabora.com>

Reviewed-by: Christian König <christian.koenig@amd.com>

> ---
>   drivers/gpu/drm/drm_gem.c | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_gem.c b/drivers/gpu/drm/drm_gem.c
> index eb0c2d041f13..86d670c71286 100644
> --- a/drivers/gpu/drm/drm_gem.c
> +++ b/drivers/gpu/drm/drm_gem.c
> @@ -1226,7 +1226,7 @@ drm_gem_lock_reservations(struct drm_gem_object **objs, int count,
>   		ret = dma_resv_lock_slow_interruptible(obj->resv,
>   								 acquire_ctx);
>   		if (ret) {
> -			ww_acquire_done(acquire_ctx);
> +			ww_acquire_fini(acquire_ctx);
>   			return ret;
>   		}
>   	}
> @@ -1251,7 +1251,7 @@ drm_gem_lock_reservations(struct drm_gem_object **objs, int count,
>   				goto retry;
>   			}
>   
> -			ww_acquire_done(acquire_ctx);
> +			ww_acquire_fini(acquire_ctx);
>   			return ret;
>   		}
>   	}

_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization

       reply	other threads:[~2022-07-05 11:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220701090240.1896131-1-dmitry.osipenko@collabora.com>
     [not found] ` <20220701090240.1896131-2-dmitry.osipenko@collabora.com>
2022-07-05 11:33   ` Christian König via Virtualization [this message]
2022-08-09 16:44     ` [PATCH v8 1/2] drm/gem: Properly annotate WW context on drm_gem_lock_reservations() error Daniel Vetter
2022-08-10  6:52       ` Christian König via Virtualization
2022-08-10  8:33         ` Daniel Vetter
2022-08-10  9:04           ` Christian König via Virtualization
     [not found] ` <20220701090240.1896131-3-dmitry.osipenko@collabora.com>
2022-07-05 11:39   ` [PATCH v8 2/2] drm/gem: Don't map imported GEMs Christian König via Virtualization
2022-07-05 21:48     ` Rob Clark
     [not found]       ` <2a646ce4-c2ec-3b11-77a0-cc720afd6fe1@collabora.com>
2022-08-10 11:47         ` Daniel Vetter
2022-08-10 15:08           ` Rob Clark
     [not found]             ` <9674d00e-c0d6-ceba-feab-5dc475bda694@collabora.com>
2022-08-10 22:03               ` Rob Clark
     [not found]                 ` <fc019528-7ec7-9e5b-1b6d-c44da14346cf@collabora.com>
2022-08-10 23:19                   ` Rob Clark
     [not found]                     ` <73b51dde-689f-64ce-a1c8-0d7c84a2ed66@collabora.com>
2022-08-12 14:57                       ` Rob Clark
2022-08-12 15:01                         ` Rob Clark
     [not found]                           ` <5f118e10-db7a-a128-1e87-c9dddb65b2ac@collabora.com>
2022-08-16 12:03                             ` Christian König
     [not found]                               ` <cf8cd8da-08d2-5e70-a239-2a67da37c9ea@collabora.com>
     [not found]                                 ` <e9bde303-6474-aa0b-7880-cf7d8b163983@collabora.com>
2022-08-23 10:01                                   ` Christian König
2022-08-23 16:47                                     ` Rob Clark
     [not found]                                       ` <bab5a55b-cbd3-4119-af39-794e38f5a0ee@collabora.com>
2022-09-11 18:00                                         ` Rob Clark
2022-08-16 22:18                             ` Rob Clark

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=a42237c9-6304-4b06-cede-2175c7e7b87d@amd.com \
    --to=virtualization@lists.linux-foundation.org \
    --cc=airlied@linux.ie \
    --cc=christian.koenig@amd.com \
    --cc=daniel@ffwll.ch \
    --cc=digetx@gmail.com \
    --cc=dmitry.osipenko@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emil.l.velikov@gmail.com \
    --cc=gurchetansingh@chromium.org \
    --cc=kernel@collabora.com \
    --cc=kraxel@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=olvaffe@gmail.com \
    --cc=thomas_os@shipmail.org \
    --cc=tzimmermann@suse.de \
    /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;
as well as URLs for NNTP newsgroup(s).