After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 790457 - extract/gstreamer: blacklist video4linux2 GStreamer plugin
extract/gstreamer: blacklist video4linux2 GStreamer plugin
Status: RESOLVED FIXED
Product: tracker
Classification: Core
Component: Miners
unspecified
Other All
: Normal normal
: ---
Assigned To: tracker-general
tracker-general
Depends on:
Blocks:
 
 
Reported: 2017-11-16 18:17 UTC by robert
Modified: 2017-11-17 14:56 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
extract/gstreamer: blacklist via plugin rather than feature (1.75 KB, patch)
2017-11-16 18:17 UTC, robert
accepted-commit_now Details | Review
extract/gstreamer: blacklist video4linux2 plugin (1.03 KB, patch)
2017-11-16 18:17 UTC, robert
accepted-commit_now Details | Review

Description robert 2017-11-16 18:17:15 UTC
Tweak the blacklisting code in the GStreamer extractor to match the
blacklisted elememts by plugin, and then blacklist video4linux2 so
the extractor won't consume V4L2 decode units and block real playback.
It's not posible to match V4L2 by feature as they are dynamically
generated based on available units, and this simplifies maintenance
of the other blacklists for similar reasons.
Comment 1 robert 2017-11-16 18:17:19 UTC
Created attachment 363856 [details] [review]
extract/gstreamer: blacklist via plugin rather than feature

Using a features-based blacklist means that you need to keep adding
new blacklist entries when new codecs are added, and makes it impossible
to match plugins which generate features dynamically based on
detected hardware.
Comment 2 robert 2017-11-16 18:17:24 UTC
Created attachment 363857 [details] [review]
extract/gstreamer: blacklist video4linux2 plugin

Avoid attempting to use V4L2 hardware-accelerated decoders, which
can keep scarce hardware units busy and prevent user-facing applications
from using hardware accelerated decode.
Comment 3 robert 2017-11-16 18:24:41 UTC
(fwiw I'll also submit the same change to the same blacklisting code in Totem!)
Comment 4 Carlos Garnacho 2017-11-16 19:35:29 UTC
Review of attachment 363856 [details] [review]:

Assuming bcmdec is still blacklisted as the module name matches, seems more correct and cleaner, nice :)
Comment 5 Carlos Garnacho 2017-11-16 19:35:46 UTC
Review of attachment 363857 [details] [review]:

Makes sense.
Comment 6 robert 2017-11-17 12:08:07 UTC
I checked both vaapi and bcmdec are registered with those plugin names, and the blacklisting certainly works for v4l2 as I was testing this all on an ARM box (how I found the seccomp snafu!).
Comment 7 robert 2017-11-17 14:56:31 UTC
Pushed.