From mboxrd@z Thu Jan  1 00:00:00 1970
From: Robert Foss <robert.foss@collabora.com>
Subject: Re: [PATCH v2] drm/msm: Move fence put to where failure occurs
Date: Fri, 2 Nov 2018 13:30:48 +0100
Message-ID: <0e882e0f-07a0-e217-6e88-082a09e87986@collabora.com>
References: <20181102121313.23271-1-robert.foss@collabora.com>
 <154116100076.30246.13155169401499183452@skylake-alporthouse-com>
Mime-Version: 1.0
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <linux-kernel-owner@vger.kernel.org>
In-Reply-To: <154116100076.30246.13155169401499183452@skylake-alporthouse-com>
Content-Language: en-US
Sender: linux-kernel-owner@vger.kernel.org
To: Chris Wilson <chris@chris-wilson.co.uk>, dri-devel@lists.freedesktop.org, freedreno@lists.freedesktop.org, linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
List-Id: linux-arm-msm@vger.kernel.org

Hey Chris,

On 2018-11-02 13:16, Chris Wilson wrote:
> Quoting Robert Foss (2018-11-02 12:13:13)
>> If dma_fence_wait fails to wait for a supplied in-fence in
>> msm_ioctl_gem_submit, make sure we release that in-fence.
>>
>> Also remove this dma_fence_put() from the 'out' label.
>>
>> Signed-off-by: Robert Foss <robert.foss@collabora.com>
> 
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>

Danke!

> 
> Rob, this probably merits a cc:stable tag -- if the wait was interrupted
> by a signal, the fence would be leaked.

Ack, CC-ed the v2 submission.


Rob.