From: Tristan Matthews via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Tristan Matthews <httamt@protonmail.com>
Subject: Re: [FFmpeg-devel] [PATCH] checkasm/h264dsp: Fix stack-buffer-overflow, effective-type violations
Date: Mon, 16 Jun 2025 15:01:13 +0000
Message-ID: <mailman.3397.1750086084.1384.ffmpeg-devel@ffmpeg.org> (raw)
In-Reply-To: <GV1P250MB0737D914E02C767118103D5C8F70A@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM>
[-- Attachment #1: Type: message/rfc822, Size: 2216 bytes --]
From: Tristan Matthews <httamt@protonmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] checkasm/h264dsp: Fix stack-buffer-overflow, effective-type violations
Date: Mon, 16 Jun 2025 15:01:13 +0000
Message-ID: <vegvlCZHYYZ6aGheYxo60zMeb6fbvVfr7hJcX_-uO8XMCam0z3M7A-9cbOujaNCmpIo94ivVtjjrUP8jojeLdzZ5kO2s1yBSLwLDMH3x_EM=@protonmail.com>
Sent with Proton Mail secure email.
On Monday, June 16th, 2025 at 6:53 AM, Andreas Rheinhardt <andreas.rheinhardt@outlook.com> wrote:
> Patch attached.
>
LGTM, and sorry about that, for future reference did you do anything in particular (instrumentation wise) to catch the stack overflow? I tried make fate on a few different machines and didn't hit that.
Best,
Tristan
[-- 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 prev parent reply other threads:[~2025-06-16 15:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 10:53 Andreas Rheinhardt
2025-06-16 15:01 ` Tristan Matthews via ffmpeg-devel [this message]
2025-06-16 18:21 ` Andreas Rheinhardt
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=mailman.3397.1750086084.1384.ffmpeg-devel@ffmpeg.org \
--to=ffmpeg-devel@ffmpeg.org \
--cc=httamt@protonmail.com \
/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