From patchwork Wed May 29 11:37:23 2024 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Janusz Krzysztofik X-Patchwork-Id: 13678738 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 6209FC27C43 for ; Wed, 29 May 2024 11:38:50 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 5EC4810E19E; Wed, 29 May 2024 11:38:49 +0000 (UTC) Authentication-Results: gabe.freedesktop.org; dkim=pass (2048-bit key; unprotected) header.d=intel.com header.i=@intel.com header.b="GRZIj+q+"; dkim-atps=neutral Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.16]) by gabe.freedesktop.org (Postfix) with ESMTPS id C37EC10E19E; Wed, 29 May 2024 11:38:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1716982727; x=1748518727; h=from:to:cc:subject:date:message-id:mime-version: content-transfer-encoding; bh=4vu2ceW7/xEeRmdJa9CJ4taLxNbOWkh62uc3BBoCJi8=; b=GRZIj+q+EKyj8gY8/SSCr+B/HFWPibnLOw9RJbyEkl1nn0/vO0fMIZzw 7v0W/EBjd21QAJdGu5YeUHN69BcdCnid3p131hZuK6fcV5rG8MN5HtkYj qZZoCNzmJVe5w8LT/GTTaLOVvIU/kmemzCXMWKE2xX7+PnOlq9e1yOYoE SnwHKUZzeG98FRw/bjF4PEA/PEAmHFKxGChBErL+AiIL2bKSz8qUcolCF EZDMhhD5RJOAq7ltG4Gr9Zqxf83J1VMC5kf2hmpQmRddDdx4LfZ0mwR+K GcDqEatd1AELfK3julAkmGbEL+EmsOW2rEF3WjmnzhkN6F9PFcJU+DaDD A==; X-CSE-ConnectionGUID: 087udSwrSnqTmNVLwwkLdQ== X-CSE-MsgGUID: 2TohzRVGTMyKm0/WrAk1Rg== X-IronPort-AV: E=McAfee;i="6600,9927,11085"; a="11747824" X-IronPort-AV: E=Sophos;i="6.08,198,1712646000"; d="scan'208";a="11747824" Received: from orviesa001.jf.intel.com ([10.64.159.141]) by fmvoesa110.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 May 2024 04:38:44 -0700 X-CSE-ConnectionGUID: +oq6M5OgT4SD4TbHumPsfA== X-CSE-MsgGUID: gt2/hQXJQrq8bGcaRHKZUg== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.08,198,1712646000"; d="scan'208";a="72860795" Received: from jkrzyszt-mobl2.ger.corp.intel.com (HELO jkrzyszt-mobl2.intranet) ([10.213.20.171]) by smtpauth.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 May 2024 04:38:36 -0700 From: Janusz Krzysztofik To: intel-gfx@lists.freedesktop.org Cc: dri-devel@lists.freedesktop.org, Jani Nikula , Joonas Lahtinen , Rodrigo Vivi , Tvrtko Ursulin , Andi Shyti , Jonathan Cavitt , Janusz Krzysztofik Subject: [PATCH] drm/i915/selftest_hangcheck: Fix potential UAF after HW fence revoke Date: Wed, 29 May 2024 13:37:23 +0200 Message-ID: <20240529113809.145084-2-janusz.krzysztofik@linux.intel.com> X-Mailer: git-send-email 2.45.1 MIME-Version: 1.0 X-BeenThere: intel-gfx@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Intel graphics driver community testing & development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: intel-gfx-bounces@lists.freedesktop.org Sender: "Intel-gfx" CI is sporadically reporting the following issue triggered by igt@i915_selftest@live@hangcheck test case: <6> [414.049203] i915: Running intel_hangcheck_live_selftests/igt_reset_evict_fence ... <6> [414.068804] i915 0000:00:02.0: [drm] GT0: GUC: submission enabled <6> [414.068812] i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled <3> [414.070354] Unable to pin Y-tiled fence; err:-4 <3> [414.071282] i915_vma_revoke_fence:301 GEM_BUG_ON(!i915_active_is_idle(&fence->active)) ... <4>[ 609.603992] ------------[ cut here ]------------ <2>[ 609.603995] kernel BUG at drivers/gpu/drm/i915/gt/intel_ggtt_fencing.c:301! <4>[ 609.604003] invalid opcode: 0000 [#1] PREEMPT SMP NOPTI <4>[ 609.604006] CPU: 0 PID: 268 Comm: kworker/u64:3 Tainted: G U W 6.9.0-CI_DRM_14785-g1ba62f8cea9c+ #1 <4>[ 609.604008] Hardware name: Intel Corporation Alder Lake Client Platform/AlderLake-P DDR4 RVP, BIOS RPLPFWI1.R00.4035.A00.2301200723 01/20/2023 <4>[ 609.604010] Workqueue: i915 __i915_gem_free_work [i915] <4>[ 609.604149] RIP: 0010:i915_vma_revoke_fence+0x187/0x1f0 [i915] ... <4>[ 609.604271] Call Trace: <4>[ 609.604273] ... <4>[ 609.604716] __i915_vma_evict+0x2e9/0x550 [i915] <4>[ 609.604852] __i915_vma_unbind+0x7c/0x160 [i915] <4>[ 609.604977] force_unbind+0x24/0xa0 [i915] <4>[ 609.605098] i915_vma_destroy+0x2f/0xa0 [i915] <4>[ 609.605210] __i915_gem_object_pages_fini+0x51/0x2f0 [i915] <4>[ 609.605330] __i915_gem_free_objects.isra.0+0x6a/0xc0 [i915] <4>[ 609.605440] process_scheduled_works+0x351/0x690 Since no other tests nor users report that issue, I believe it is specific to that test case, which should just wait after reset it triggers for actual completion of a request that it forced to claim using a hardware fence before it releases allocated resources. Fix it. Signed-off-by: Janusz Krzysztofik Reviewed-by: Jonathan Cavitt --- drivers/gpu/drm/i915/gt/selftest_hangcheck.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/gpu/drm/i915/gt/selftest_hangcheck.c b/drivers/gpu/drm/i915/gt/selftest_hangcheck.c index 9ce8ff1c04fe5..b47c99f38a525 100644 --- a/drivers/gpu/drm/i915/gt/selftest_hangcheck.c +++ b/drivers/gpu/drm/i915/gt/selftest_hangcheck.c @@ -1568,6 +1568,8 @@ static int __igt_reset_evict_vma(struct intel_gt *gt, out_rq: i915_request_put(rq); + if (flags & EXEC_OBJECT_NEEDS_FENCE) + i915_active_wait(&arg.vma->fence->active); out_obj: i915_gem_object_put(obj); fini: