git.videolan.org Git - ffmpeg.git/rss log

FFmpeg git repo

http://git.videolan.org/?p=ffmpeg.git;a=summary

Les articles publiés sur le site

  • avcodec/opus/parser : set duration when complete frames are fed

    3 janvier, par James Almer
    avcodec/opus/parser: set duration when complete frames are fed

Fixes a regression since 873a34c129869e551cb7d3d2445e28c0ba079948.

Signed-off-by: James Almer <jamrial@gmail.com>
    • [DH] libavcodec/opus/parser.c

  • avcodec/opus/parser : reindent after the previous commit

    3 janvier, par James Almer
    avcodec/opus/parser: reindent after the previous commit

Signed-off-by: James Almer <jamrial@gmail.com>
    • [DH] libavcodec/opus/parser.c

  • vp9 : recon : Use emulated edge to prevent buffer overflows

    3 janvier, par Janne Grunau
    vp9: recon: Use emulated edge to prevent buffer overflows

The arm/aarch64 horizontal filter reads one additional pixel beyond what
the filter uses. This can become an issue if the application does not
allocate larger buffers than what's required for the pixel data. If the
motion vector points to the bottom right edge of the picture this
becomes a read buffer overflow. This triggers segfaults in Firefox for
video resolutions which result in a page aligned picture size like
1280x640.
Prevent this by using emulated edge in this case.

Fixes: https://bugzilla.mozilla.org/show_bug.cgi?id=1881185
Signed-off-by: Janne Grunau <janne-ffmpeg@jannau.net>
Signed-off-by: Ronald S. Bultje <rsbultje@gmail.com>
    • [DH] libavcodec/vp9recon.c

  • arm : vp9mc : Load only 12 pixels in the 4 pixel wide horizontal filter

    3 janvier, par Janne Grunau
    arm: vp9mc: Load only 12 pixels in the 4 pixel wide horizontal filter

This reduces the amount the horizontal filters read beyond the filter
width to a consistent 1 pixel. The data is not used so this is usually
not noticeable. It becomes a problem when the application allocates
frame buffers only for the aligned picture size and the end of it is at
a page boundary. This happens for picture sizes which are a multiple of
the page size like 1280x640. The frame buffer allocation is based on
its most likely done via mmap + MAP_ANONYMOUS so start and end of the
buffer are page aligned and the previous and next page are not
necessarily mapped.
This mirrors the aarch64 change.

Signed-off-by: Janne Grunau <janne-ffmpeg@jannau.net>
Signed-off-by: Ronald S. Bultje <rsbultje@gmail.com>
    • [DH] libavcodec/arm/vp9mc_neon.S

  • aarch64 : vp9mc : Load only 12 pixels in the 4 pixel wide horizontal filter

    3 janvier, par Janne Grunau
    aarch64: vp9mc: Load only 12 pixels in the 4 pixel wide horizontal filter

This reduces the amount the horizontal filters read beyond the filter
width to a consistent 1 pixel. The data is not used so this is usually
not noticeable. It becomes a problem when the application allocates
frame buffers only for the aligned picture size and the end of it is at
a page boundary. This happens for picture sizes which are a multiple of
the page size like 1280x640. The frame buffer allocation is based on
its most likely done via mmap + MAP_ANONYMOUS so start and end of the
buffer are page aligned and the previous and next page are not
necessarily mapped.
Under these conditions like seen by Firefox a read beyond the end of the
buffer results in a segfault.
After the over-read is reduced to a single pixel it's reasonable to use
VP9's emulated edge motion compensation for this.

Fixes: https://bugzilla.mozilla.org/show_bug.cgi?id=1881185
Signed-off-by: Janne Grunau <janne-ffmpeg@jannau.net>
Signed-off-by: Ronald S. Bultje <rsbultje@gmail.com>
    • [DH] libavcodec/aarch64/vp9mc_neon.S

Navigation

Sites Web