From: Christophe Gisquet via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: 0xBat <monsterbat02@gmail.com>,
Christophe Gisquet <christophe.gisquet@gmail.com>
Subject: [FFmpeg-devel] Re: [PATCH] avcodec/vvc: add boundary checks for CTU table access
Date: Tue, 6 Jan 2026 20:35:04 +0100
Message-ID: <CAPYFPM3f1SLSdsjO5nyKoSJBHMHXTN-dRpPLxDMPzZ6gEPk-Og@mail.gmail.com> (raw)
In-Reply-To: <CAPYFPM2hJmLrHHjcK=PWuq5aM5hSp9nKStb-W94ttfumvbuWOw@mail.gmail.com>
Le mar. 6 janv. 2026, 09:01, Christophe Gisquet <
christophe.gisquet@gmail.com> a écrit
> So lines that are processed are ok if overflowing. It sounds like width
>
I meant previous lines. Which can be an okish optimization sometimes but
maybe not here.
>
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
prev parent reply other threads:[~2026-01-06 19:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-05 0:16 [FFmpeg-devel] " 0xBat via ffmpeg-devel
2026-01-05 0:16 ` [FFmpeg-devel] [PATCH] avcodec/vvc: clamp palette predictor size 0xBat via ffmpeg-devel
2026-01-05 0:16 ` [FFmpeg-devel] [PATCH] avcodec/vvc: validate reference picture list indices 0xBat via ffmpeg-devel
2026-01-06 7:58 ` [FFmpeg-devel] " Christophe Gisquet via ffmpeg-devel
2026-01-06 8:47 ` Frank Plowman via ffmpeg-devel
2026-01-06 8:01 ` [FFmpeg-devel] Re: [PATCH] avcodec/vvc: add boundary checks for CTU table access Christophe Gisquet via ffmpeg-devel
2026-01-06 19:35 ` Christophe Gisquet via ffmpeg-devel [this message]
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=CAPYFPM3f1SLSdsjO5nyKoSJBHMHXTN-dRpPLxDMPzZ6gEPk-Og@mail.gmail.com \
--to=ffmpeg-devel@ffmpeg.org \
--cc=christophe.gisquet@gmail.com \
--cc=monsterbat02@gmail.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