From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: "Willy R. Vasquez" <wrv@utexas.edu>, Hovav Shacham <hovav@cs.utexas.edu>
Subject: [FFmpeg-devel] [RFC] d3dva security hw+threads
Date: Fri, 2 Sep 2022 01:32:36 +0200
Message-ID: <20220901233236.GP2088045@pb2> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1071 bytes --]
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 ...
There where 2 patches posted by the maintainer, neither really felt "right" and
also indepandently noone else applied either or approved either.
What is the preferred way of the community to handle this (and similar issues)?
ignore it and hope it will be handled by someone else ?
document it in release notes ?
disable the code ? (and which code)
And yes iam trying to be a bit annoying here, so this moves forward and
a fix or workaround can be in git master soon and then the next releases
Thanks
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
The real ebay dictionary, page 1
"Used only once" - "Some unspecified defect prevented a second use"
"In good condition" - "Can be repaird by experienced expert"
"As is" - "You wouldnt want it even if you were payed for it, if you knew ..."
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
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".
next reply other threads:[~2022-09-01 23:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 23:32 Michael Niedermayer [this message]
2022-09-01 23:46 ` Timo Rothenpieler
2022-09-02 1:43 ` Lynne
2022-09-04 6:58 ` Anton Khirnov
2022-09-04 7:43 ` Soft Works
2022-09-05 5:59 ` Anton Khirnov
2022-09-05 19:41 ` Soft Works
2022-09-05 15:50 ` Lukas Fellechner
2022-09-05 16:13 ` Anton Khirnov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220901233236.GP2088045@pb2 \
--to=michael@niedermayer.cc \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=hovav@cs.utexas.edu \
--cc=wrv@utexas.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git