Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp766601rwb; Thu, 10 Nov 2022 07:11:12 -0800 (PST) X-Google-Smtp-Source: AMsMyM4T5LTSlsrAROA6Dkq0qt5+etU9SqI0knd6Vs8GkPxzi3DNJ9rud0SnUPHPHKZ525RMVgnW X-Received: by 2002:a17:907:1381:b0:78a:52bb:d904 with SMTP id vs1-20020a170907138100b0078a52bbd904mr2894503ejb.630.1668093072064; Thu, 10 Nov 2022 07:11:12 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1668093072; cv=none; d=google.com; s=arc-20160816; b=hwIbqEOPvjxwuau9AEnyERWpek9qQ1OLqIkbq4rd4UaKHIJikJOEpy9VVWbP/4mJEN UquGSZLI+xNT75atec9kmuFWosV8JOnmBe2tWeTNf6y+kIHnOP76q6uRk/VlYGt5lN5Y f6ek33kRcX/hvEwTqMCcvgReCyVBWdl7Fo8WzmGEQ8sG3lxP+wqEi1M1n3yO8iDNm3Fp 5cRomA3+6e5FnxnGpdFkNC01OodL+07/yknbIDPeZpBZPfiMG+WWOVqg5Wnmk6+6Airg LW5KWFPqDvm2g6nKarIrCzXclCbHV3pQZTUvXxPPUC6peqEhA5GentoZIQm+UVnnXTcV pKDA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id:dkim-signature; bh=jeojWIb7VQpFRqeY9szvQNRfqJ9IH89UkKgIa2DfpJs=; b=Ag6EPK/VA+tVSKTSY4v6I7ph0q0MvRjhVsQSYjRs2hCoxFN3LvW7Qm43L3Q1eRo3NV g0uOVhAA6PsayJir+jUyt+wfFfpSepg0/zvm4HmQHLoGwuhrmpyGOiPl0IdTJ7SuhD/H Yd2VgO1mEydAWIURnXcjCgGZQV14tnAI9zf/JuCc9RMrUXXiFG/Z4oLyhzFYYTt5uW+m L+7z4fAxSjlsfvfm41aNDl980cAdbyMw14MN0180dMW9HcLMhqwckNH58l6lAmQGSwM7 PndBiYDU0JUr508qMTW4eUYDMpZBz0+R1nDCLHIdKOKgkDBxtjyT8SJ7PCFwNrCVzBQh nwnQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=WEXqkUpG; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id j8-20020aa7c0c8000000b0044f1b7b8713si15739684edp.281.2022.11.10.07.10.27; Thu, 10 Nov 2022 07:11:12 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=WEXqkUpG; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231292AbiKJOuI (ORCPT + 92 others); Thu, 10 Nov 2022 09:50:08 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39940 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231349AbiKJOuE (ORCPT ); Thu, 10 Nov 2022 09:50:04 -0500 Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id AF140663E8 for ; Thu, 10 Nov 2022 06:50:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1668091801; x=1699627801; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=7MxnbuTAE3WAWNVc0OdZyWz/GDjq9W/RdOjM4WTr/2c=; b=WEXqkUpGO8LpB+fDatsm5YqE0Mo0cSBEU0zb1KszRq+LSpxh+xod0eaR xW8SyuHvm53Raq2MhL7BvxjWN4EQMO/js/zKF8wA3oCCMBiSoLwlhz1yt gUbzyYp+z8hRQkJZSFzkpHYO+5SPVuag+yY07mq+Q/PXGmwJtVM3oHLw0 4px+JhsIjjXdzAedS5kUgYwqlFddVXwoNbsL5GP1gL6yyYcD55bxHpcmA 07bckSkCfI6V/my9Dtl24HN4svdV+A0+hTqlZbfdYEDn5iFskq5f6pW9q LZCoHyd8FetB0Vuq4/li6sQwyq+zLp8v5QRWJGBHjI/x+6AuxWtMbz16e g==; X-IronPort-AV: E=McAfee;i="6500,9779,10527"; a="313098070" X-IronPort-AV: E=Sophos;i="5.96,154,1665471600"; d="scan'208";a="313098070" Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga103.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 10 Nov 2022 06:50:01 -0800 X-IronPort-AV: E=McAfee;i="6500,9779,10527"; a="726406555" X-IronPort-AV: E=Sophos;i="5.96,154,1665471600"; d="scan'208";a="726406555" Received: from inovosel-mobl3.ger.corp.intel.com (HELO [10.252.17.163]) ([10.252.17.163]) by fmsmga003-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 10 Nov 2022 06:49:55 -0800 Message-ID: <1d066cb4-fb82-bffd-5e89-97ba572be3fa@intel.com> Date: Thu, 10 Nov 2022 14:49:53 +0000 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Firefox/102.0 Thunderbird/102.4.1 Subject: Re: [PATCH] drm/i915: Fix unhandled deadlock in grab_vma() Content-Language: en-GB To: Mani Milani , LKML Cc: Tvrtko Ursulin , Maarten Lankhorst , =?UTF-8?Q?Thomas_Hellstr=c3=b6m?= , Chris Wilson , =?UTF-8?Q?Christian_K=c3=b6nig?= , Daniel Vetter , David Airlie , Jani Nikula , Joonas Lahtinen , Niranjana Vishwanathapura , Nirmoy Das , Rodrigo Vivi , dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org References: <20221110053133.2433412-1-mani@chromium.org> From: Matthew Auld In-Reply-To: <20221110053133.2433412-1-mani@chromium.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A, RCVD_IN_DNSWL_MED,SPF_HELO_NONE,SPF_NONE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/11/2022 05:31, Mani Milani wrote: > At present, the gpu thread crashes at times when grab_vma() attempts to > acquire a gem object lock when in a deadlock state. > > Problems: > I identified the following 4 issues in the current code: > 1. Since grab_vma() calls i915_gem_object_trylock(), which consequently > calls ww_mutex_trylock(), to acquire lock, it does not perform any > -EDEADLK handling; And -EALREADY handling is also unreliable, > according to the description of ww_mutex_trylock(). > 2. Since the return value of grab_vma() is a boolean showing > success/failure, it does not provide any extra information on the > failure reason, and therefore does not provide any mechanism to its > caller to take any action to fix a potential deadlock. > 3. Current grab_vma() implementation produces inconsistent behaviour > depending on the refcount value, without informing the caller. If > refcount is already zero, grab_vma() neither acquires lock nor > increments the refcount, but still returns 'true' for success! This > means that grab_vma() returning true (for success) does not always > mean that the gem obj is actually safely accessible. > 4. Currently, calling "i915_gem_object_lock(obj,ww)" is meant to be > followed by a consequent "i915_gem_object_unlock(obj)" ONLY if the > original 'ww' object pointer was NULL, or otherwise not be called and > leave the houskeeping to "i915_gem_ww_ctx_fini(ww)". There are a few > issues with this: > - This is not documented anywhere in the code (that I could find), > but only explained in an older commit message. > - This produces an inconsistent usage of the lock/unlock functions, > increasing the chance of mistakes and issues. > - This is not a clean design as it requires any new code that calls > these lock/unlock functions to know their internals, as well as the > internals of the functions calling the new code being added. > > Fix: > To fix the issues above, this patch: > 1. Changes grab_vma() to call i915_gem_object_lock() instead of > i915_gem_object_trylock(), to handle -EDEADLK and -EALREADY cases. > This should not cause any issue since the PIN_NONBLOCK flag is > checked beforehand in the 2 cases grab_vma() is called. > 2. Changes grab_vma() to return the actual error code, instead of bool. > 3. Changes grab_vma() to behave consistently when returning success, by > both incrementing the refcount and acquiring lock at all times. > 4. Changes i915_gem_object_unlock() to pair with i915_gem_object_lock() > nicely in all cases and do the housekeeping without the need for the > caller to do anything other than simply calling lock and unlock. > 5. Ensures the gem obj->obj_link is initialized and deleted from the ww > list such that it can be tested for emptiness using list_empty(). > > Signed-off-by: Mani Milani > --- > > drivers/gpu/drm/i915/gem/i915_gem_object.c | 2 + > drivers/gpu/drm/i915/gem/i915_gem_object.h | 10 ++++- > drivers/gpu/drm/i915/i915_gem_evict.c | 48 ++++++++++++---------- > drivers/gpu/drm/i915/i915_gem_ww.c | 8 ++-- > 4 files changed, 41 insertions(+), 27 deletions(-) > > diff --git a/drivers/gpu/drm/i915/gem/i915_gem_object.c b/drivers/gpu/drm/i915/gem/i915_gem_object.c > index 369006c5317f..69d013b393fb 100644 > --- a/drivers/gpu/drm/i915/gem/i915_gem_object.c > +++ b/drivers/gpu/drm/i915/gem/i915_gem_object.c > @@ -78,6 +78,8 @@ void i915_gem_object_init(struct drm_i915_gem_object *obj, > > INIT_LIST_HEAD(&obj->mm.link); > > + INIT_LIST_HEAD(&obj->obj_link); > + > INIT_LIST_HEAD(&obj->lut_list); > spin_lock_init(&obj->lut_lock); > > diff --git a/drivers/gpu/drm/i915/gem/i915_gem_object.h b/drivers/gpu/drm/i915/gem/i915_gem_object.h > index 1723af9b0f6a..7e7a61bdf52c 100644 > --- a/drivers/gpu/drm/i915/gem/i915_gem_object.h > +++ b/drivers/gpu/drm/i915/gem/i915_gem_object.h > @@ -219,7 +219,7 @@ static inline bool i915_gem_object_trylock(struct drm_i915_gem_object *obj, > return ww_mutex_trylock(&obj->base.resv->lock, &ww->ctx); > } > > -static inline void i915_gem_object_unlock(struct drm_i915_gem_object *obj) > +static inline void __i915_gem_object_unlock(struct drm_i915_gem_object *obj) > { > if (obj->ops->adjust_lru) > obj->ops->adjust_lru(obj); > @@ -227,6 +227,14 @@ static inline void i915_gem_object_unlock(struct drm_i915_gem_object *obj) > dma_resv_unlock(obj->base.resv); > } > > +static inline void i915_gem_object_unlock(struct drm_i915_gem_object *obj) > +{ > + if (list_empty(&obj->obj_link)) > + __i915_gem_object_unlock(obj); > + else > + i915_gem_ww_unlock_single(obj); > +} > + > static inline void > i915_gem_object_set_readonly(struct drm_i915_gem_object *obj) > { > diff --git a/drivers/gpu/drm/i915/i915_gem_evict.c b/drivers/gpu/drm/i915/i915_gem_evict.c > index f025ee4fa526..3eb514b4eddc 100644 > --- a/drivers/gpu/drm/i915/i915_gem_evict.c > +++ b/drivers/gpu/drm/i915/i915_gem_evict.c > @@ -55,29 +55,33 @@ static int ggtt_flush(struct intel_gt *gt) > return intel_gt_wait_for_idle(gt, MAX_SCHEDULE_TIMEOUT); > } > > -static bool grab_vma(struct i915_vma *vma, struct i915_gem_ww_ctx *ww) > +static int grab_vma(struct i915_vma *vma, struct i915_gem_ww_ctx *ww) > { > + int err; > + > + /* Dead objects don't need pins */ > + if (dying_vma(vma)) > + atomic_and(~I915_VMA_PIN_MASK, &vma->flags); > + > + err = i915_gem_object_lock(vma->obj, ww); AFAIK the issue here is that we are already holding the vm->mutex, so this can potentially deadlock, which I guess is why this was trylock. We typically grab a bunch of object locks during execbuf, and then grab the vm->mutex, before binding the vma for each object. So vm->mutex is always our inner lock, and the object lock is the outer one. Using a full lock here then inverts that locking AFAICT. Like say if one process is holding object A + vm->mutex and then tries to grab object B here in grab_vma(), but another process is already holding object B + waiting to grab vm->mutex? > + > /* > * We add the extra refcount so the object doesn't drop to zero until > - * after ungrab_vma(), this way trylock is always paired with unlock. > + * after ungrab_vma(), this way lock is always paired with unlock. > */ > - if (i915_gem_object_get_rcu(vma->obj)) { > - if (!i915_gem_object_trylock(vma->obj, ww)) { > - i915_gem_object_put(vma->obj); > - return false; > - } > - } else { > - /* Dead objects don't need pins */ > - atomic_and(~I915_VMA_PIN_MASK, &vma->flags); > - } > + if (!err) > + i915_gem_object_get(vma->obj); > > - return true; > + return err; > } > > static void ungrab_vma(struct i915_vma *vma) > { > - if (dying_vma(vma)) > + if (dying_vma(vma)) { > + /* Dead objects don't need pins */ > + atomic_and(~I915_VMA_PIN_MASK, &vma->flags); > return; > + } > > i915_gem_object_unlock(vma->obj); > i915_gem_object_put(vma->obj); > @@ -93,10 +97,11 @@ mark_free(struct drm_mm_scan *scan, > if (i915_vma_is_pinned(vma)) > return false; > > - if (!grab_vma(vma, ww)) > + if (grab_vma(vma, ww)) > return false; > > list_add(&vma->evict_link, unwind); > + > return drm_mm_scan_add_block(scan, &vma->node); > } > > @@ -284,10 +289,12 @@ i915_gem_evict_something(struct i915_address_space *vm, > vma = container_of(node, struct i915_vma, node); > > /* If we find any non-objects (!vma), we cannot evict them */ > - if (vma->node.color != I915_COLOR_UNEVICTABLE && > - grab_vma(vma, ww)) { > - ret = __i915_vma_unbind(vma); > - ungrab_vma(vma); > + if (vma->node.color != I915_COLOR_UNEVICTABLE) { > + ret = grab_vma(vma, ww); > + if (!ret) { > + ret = __i915_vma_unbind(vma); > + ungrab_vma(vma); > + } > } else { > ret = -ENOSPC; > } > @@ -382,10 +389,9 @@ int i915_gem_evict_for_node(struct i915_address_space *vm, > break; > } > > - if (!grab_vma(vma, ww)) { > - ret = -ENOSPC; > + ret = grab_vma(vma, ww); > + if (ret) > break; > - } > > /* > * Never show fear in the face of dragons! > diff --git a/drivers/gpu/drm/i915/i915_gem_ww.c b/drivers/gpu/drm/i915/i915_gem_ww.c > index 3f6ff139478e..937b279f50fc 100644 > --- a/drivers/gpu/drm/i915/i915_gem_ww.c > +++ b/drivers/gpu/drm/i915/i915_gem_ww.c > @@ -19,16 +19,14 @@ static void i915_gem_ww_ctx_unlock_all(struct i915_gem_ww_ctx *ww) > struct drm_i915_gem_object *obj; > > while ((obj = list_first_entry_or_null(&ww->obj_list, struct drm_i915_gem_object, obj_link))) { > - list_del(&obj->obj_link); > - i915_gem_object_unlock(obj); > - i915_gem_object_put(obj); > + i915_gem_ww_unlock_single(obj); > } > } > > void i915_gem_ww_unlock_single(struct drm_i915_gem_object *obj) > { > - list_del(&obj->obj_link); > - i915_gem_object_unlock(obj); > + list_del_init(&obj->obj_link); > + __i915_gem_object_unlock(obj); > i915_gem_object_put(obj); > } >