From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <ffmpeg-devel-bounces@ffmpeg.org>
Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100])
	by master.gitmailbox.com (Postfix) with ESMTP id BF588441BB
	for <ffmpegdev@gitmailbox.com>; Fri,  2 Sep 2022 01:43:48 +0000 (UTC)
Received: from [127.0.1.1] (localhost [127.0.0.1])
	by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 9CFEB68BA1A;
	Fri,  2 Sep 2022 04:43:45 +0300 (EEST)
Received: from w4.tutanota.de (w4.tutanota.de [81.3.6.165])
 by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 017B268BA14
 for <ffmpeg-devel@ffmpeg.org>; Fri,  2 Sep 2022 04:43:38 +0300 (EEST)
Received: from w3.tutanota.de (unknown [192.168.1.164])
 by w4.tutanota.de (Postfix) with ESMTP id 2F68D1060247
 for <ffmpeg-devel@ffmpeg.org>; Fri,  2 Sep 2022 01:43:38 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1662083017; 
 s=s1; d=lynne.ee;
 h=From:From:To:To:Subject:Subject:Content-Description:Content-ID:Content-Type:Content-Type:Content-Transfer-Encoding:Content-Transfer-Encoding:Cc:Date:Date:In-Reply-To:In-Reply-To:MIME-Version:MIME-Version:Message-ID:Message-ID:Reply-To:References:References:Sender;
 bh=3FYu8Qp/uyDQGX3Fz3IcBMCCB0XnapbJUbIHWm6+eGM=;
 b=MwEopCfw+YQkLhzRkuX1DkgLKcykU/ARQ1Z8ZBC2bFf5f8L/Wgs7FIN61kk5X+Rh
 iFtmadJ+SHN1vZv5fwC82ZQojsf/hFPZrXyVAPy06+dtJUhlNhHvQlmpc9p8JW9eUvS
 FZoAj3LCeUhA5554vF2xaH4sosBqs9Ii5wTDHtOqNU008SzyFJFmlYAp/hR54Ec/4Qk
 5qXJXT/5ndZtHQmk5wrIuRcQJDsvKMWUxP9tZ3G3iqIBps5jCoVmNIzRHXl8Nck53Df
 Cktuoc2AiWLR0DO3Rf2NeXtEjFibsID6ox+zzScOFfYfzVHWldT4knkc176E5UEtCM2
 n1z8oRvhbw==
Date: Fri, 2 Sep 2022 03:43:37 +0200 (CEST)
From: Lynne <dev@lynne.ee>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Message-ID: <NAvrXiG--3-2@lynne.ee>
In-Reply-To: <e5ca47f5-709a-ed78-9f81-fa0494069af3@rothenpieler.org>
References: <20220901233236.GP2088045@pb2>
 <e5ca47f5-709a-ed78-9f81-fa0494069af3@rothenpieler.org>
MIME-Version: 1.0
Subject: Re: [FFmpeg-devel] [RFC] d3dva security hw+threads
X-BeenThere: ffmpeg-devel@ffmpeg.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: FFmpeg development discussions and patches <ffmpeg-devel.ffmpeg.org>
List-Unsubscribe: <https://ffmpeg.org/mailman/options/ffmpeg-devel>,
 <mailto:ffmpeg-devel-request@ffmpeg.org?subject=unsubscribe>
List-Archive: <https://ffmpeg.org/pipermail/ffmpeg-devel>
List-Post: <mailto:ffmpeg-devel@ffmpeg.org>
List-Help: <mailto:ffmpeg-devel-request@ffmpeg.org?subject=help>
List-Subscribe: <https://ffmpeg.org/mailman/listinfo/ffmpeg-devel>,
 <mailto:ffmpeg-devel-request@ffmpeg.org?subject=subscribe>
Reply-To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ffmpeg-devel-bounces@ffmpeg.org
Sender: "ffmpeg-devel" <ffmpeg-devel-bounces@ffmpeg.org>
Archived-At: <https://master.gitmailbox.com/ffmpegdev/NAvrXiG--3-2@lynne.ee/>
List-Archive: <https://master.gitmailbox.com/ffmpegdev/>
List-Post: <mailto:ffmpegdev@gitmailbox.com>

Sep 2, 2022, 01:46 by timo@rothenpieler.org:

> On 02.09.2022 01:32, Michael Niedermayer wrote:
>
>> Hi all
>>
>> Theres a use after free issue in H.264 Decoding on d3d11va with multiple threads
>> I dont have the hardware/platform nor do i know the hw decoding code so i made
>> no attempt to fix this beyond asking others to ...
>>
>
> hwaccel with multiple threads being broken is not exactly a surprise.
> So we could just disable that, and always have it be one single thread?
>

Is it an API problem or a lavc problem?
Vulkan does allow for threaded submission, so I'd rather keep the option open.
We could add a new codec cap.

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".