From: Emil Velikov <emil.l.velikov@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Cc: Mark Thompson <sw@jkqxz.net>, emil.l.velikov@gmail.com
Subject: [FFmpeg-devel] [PATCH 1/3] hwcontext_vaapi: do not link against libva-x11.so
Date: Tue, 19 Jul 2022 17:56:02 +0100
Message-ID: <20220719165604.640770-1-emil.l.velikov@gmail.com> (raw)
From: Emil Velikov <emil.velikov@collabora.com>
There is an internal ABI between libva.so the libva-XXX.so libraries.
With a recent change, the internal va_fool API was removed breaking the
ABI. So if libva.so and libva-x11.so are from different version, the
whole stack will crash.
Instead we can dlopen() the libva-x11 library and gracefully error out.
Cc: Mark Thompson <sw@jkqxz.net>
Signed-off-by: Emil Velikov <emil.velikov@collabora.com>
---
Greetings team, please consider backporting this for the stable
releases.
I've noticed that we've got plenty of pre-existing memory and state
leaks in vaapi_device_create(). Would it make sense to fix those up? If
so I can follow-up with a patch.
---
configure | 2 +-
libavutil/hwcontext_vaapi.c | 34 +++++++++++++++++++++++++++++++++-
2 files changed, 34 insertions(+), 2 deletions(-)
diff --git a/configure b/configure
index 18d9b61a99..ab2a29544c 100755
--- a/configure
+++ b/configure
@@ -3816,7 +3816,7 @@ swscale_suggest="libm stdatomic"
avcodec_extralibs="pthreads_extralibs iconv_extralibs dxva2_extralibs"
avfilter_extralibs="pthreads_extralibs"
-avutil_extralibs="d3d11va_extralibs nanosleep_extralibs pthreads_extralibs vaapi_drm_extralibs vaapi_x11_extralibs vdpau_x11_extralibs"
+avutil_extralibs="d3d11va_extralibs nanosleep_extralibs pthreads_extralibs vaapi_drm_extralibs vdpau_x11_extralibs"
# programs
ffmpeg_deps="avcodec avfilter avformat"
diff --git a/libavutil/hwcontext_vaapi.c b/libavutil/hwcontext_vaapi.c
index c3a98bc4b1..e44d324928 100644
--- a/libavutil/hwcontext_vaapi.c
+++ b/libavutil/hwcontext_vaapi.c
@@ -18,8 +18,16 @@
#include "config.h"
+#if CONFIG_VAAPI_1
+# define VA_ABI ".2"
+#else
+# define VA_ABI ".1"
+#endif
+
#if HAVE_VAAPI_X11
# include <va/va_x11.h>
+# include <dlfcn.h>
+# define VA_X11_LIB "libva-x11.so" VA_ABI
#endif
#if HAVE_VAAPI_DRM
# include <va/va_drm.h>
@@ -54,6 +62,7 @@
typedef struct VAAPIDevicePriv {
#if HAVE_VAAPI_X11
+ void *libva_x11;
Display *x11_display;
#endif
@@ -1565,6 +1574,8 @@ static void vaapi_device_free(AVHWDeviceContext *ctx)
vaTerminate(hwctx->display);
#if HAVE_VAAPI_X11
+ if (priv->libva_x11)
+ dlclose(priv->libva_x11);
if (priv->x11_display)
XCloseDisplay(priv->x11_display);
#endif
@@ -1723,14 +1734,35 @@ static int vaapi_device_create(AVHWDeviceContext *ctx, const char *device,
#if HAVE_VAAPI_X11
if (!display && try_x11) {
+ VADisplay (*GetDisplay)(Display *dpy);
+
+ priv->libva_x11 = dlopen(VA_X11_LIB, RTLD_NOW | RTLD_LOCAL);
+ if (!priv->libva_x11) {
+ av_log(ctx, AV_LOG_ERROR, "Cannot open %s library %s.\n",
+ VA_X11_LIB, dlerror());
+ return AVERROR_UNKNOWN;
+ }
+
+ GetDisplay = dlsym(priv->libva_x11, "vaGetDisplay");
+ if (!GetDisplay) {
+ av_log(ctx, AV_LOG_ERROR, "Cannot retrieve %s entrypoint %s.\n",
+ "vaGetDisplay", dlerror());
+ // Always dlclose after the dlerror(). The former can alter the
+ // error string returned by the latter.
+ dlclose(priv->libva_x11);
+ return AVERROR_UNKNOWN;
+ }
+
// Try to open the device as an X11 display.
priv->x11_display = XOpenDisplay(device);
if (!priv->x11_display) {
+ dlclose(priv->libva_x11);
av_log(ctx, AV_LOG_VERBOSE, "Cannot open X11 display "
"%s.\n", XDisplayName(device));
} else {
- display = vaGetDisplay(priv->x11_display);
+ display = GetDisplay(priv->x11_display);
if (!display) {
+ dlclose(priv->libva_x11);
av_log(ctx, AV_LOG_ERROR, "Cannot open a VA display "
"from X11 display %s.\n", XDisplayName(device));
return AVERROR_UNKNOWN;
--
2.37.0
_______________________________________________
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-07-19 16:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 16:56 Emil Velikov [this message]
2022-07-19 16:56 ` [FFmpeg-devel] [PATCH 2/3] hwcontext_vaapi: do not link against libva-drm.so Emil Velikov
2022-07-19 16:56 ` [FFmpeg-devel] [PATCH 3/3] hwcontext_vaapi: #if guard VAAPI_DRM specifics Emil Velikov
2022-07-19 16:56 [FFmpeg-devel] [PATCH 0/3] hwcontext_vaapi: dlopen libva-x11 and libva-drm Emil Velikov
2022-07-19 16:56 ` [FFmpeg-devel] [PATCH 1/3] hwcontext_vaapi: do not link against libva-x11.so Emil Velikov
2022-07-19 22:11 ` Michael Niedermayer
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=20220719165604.640770-1-emil.l.velikov@gmail.com \
--to=emil.l.velikov@gmail.com \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=sw@jkqxz.net \
/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