From mboxrd@z Thu Jan 1 00:00:00 1970 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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 707C9EB64D8 for ; Thu, 22 Jun 2023 13:56:25 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231143AbjFVN4X (ORCPT ); Thu, 22 Jun 2023 09:56:23 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50150 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231134AbjFVN4T (ORCPT ); Thu, 22 Jun 2023 09:56:19 -0400 Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B0EA4199B; Thu, 22 Jun 2023 06:56:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1687442178; x=1718978178; h=date:from:to:cc:subject:message-id:references: mime-version:content-transfer-encoding:in-reply-to; bh=iwvWjTXOATc+/cgzxfPqHvCL/9Mmo5XEzzxlVw4W7tY=; b=eU8ALiWHbzzojEw+on4Ad/Lr4y8ajV/2sC1uEFU7T2oVMRhVps303hho fyu34K+3FR6Le7rWLCnS5v9wItVFZb+WrofOl1RxZQKJhEPeG9sezM5cu ACcvCPlMYQjTuLi9sEEuCjSwXnCg5r+tEya32nlmcPbiJK/CIx82SKe/a StLBxVc/U6zHftiW2Z7c6PQxn16Gr//PN/4EeTQrjlo1S454JwMVHJvca T3iAzRK54hMHAiaI/kj8OEtx4JfUiTUKk7QwCueMHhEDm5DGQ1aKsw8rv OaBOrPN0qdolbOdwp3j+IQzcsrXY2cpo/d/z3bEOCt8EfxUEOaMoiysds w==; X-IronPort-AV: E=McAfee;i="6600,9927,10748"; a="390236806" X-IronPort-AV: E=Sophos;i="6.01,263,1684825200"; d="scan'208";a="390236806" Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga101.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 22 Jun 2023 06:56:11 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10748"; a="804794065" X-IronPort-AV: E=Sophos;i="6.01,263,1684825200"; d="scan'208";a="804794065" Received: from akivisil-mobl.ger.corp.intel.com (HELO intel.com) ([10.251.215.96]) by fmsmga003-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 22 Jun 2023 06:56:09 -0700 Date: Thu, 22 Jun 2023 15:56:06 +0200 From: Andi Shyti To: Thomas =?iso-8859-15?Q?Hellstr=F6m?= Cc: intel-xe@lists.freedesktop.org, Christian =?iso-8859-15?Q?K=F6nig?= , intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org, stable@vger.kernel.org, dri-devel@lists.freedesktop.org, Christian =?iso-8859-15?Q?K=F6nig?= Subject: Re: [Intel-gfx] [PATCH 4/4] drm/ttm: Don't leak a resource on swapout move error Message-ID: References: <20230622101412.78426-1-thomas.hellstrom@linux.intel.com> <20230622101412.78426-5-thomas.hellstrom@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20230622101412.78426-5-thomas.hellstrom@linux.intel.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Thomas, On Thu, Jun 22, 2023 at 12:14:12PM +0200, Thomas Hellström wrote: > If moving the bo to system for swapout failed, we were leaking > a resource. Fix. > > Fixes: bfa3357ef9ab ("drm/ttm: allocate resource object instead of embedding it v2") > Cc: Christian König > Cc: "Christian König" > Cc: dri-devel@lists.freedesktop.org > Cc: # v5.14+ > Signed-off-by: Thomas Hellström Reviewed-by: Andi Shyti Andi