From: "Dawid Kozinski/Multimedia \(PLT\) /SRPOL/Staff Engineer/Samsung Electronics" <d.kozinski@samsung.com>
To: "'FFmpeg development discussions and patches'" <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v1] avcodec/vp9_superframe_split_bsf: Fix for possible null pointer dereference
Date: Tue, 10 Oct 2023 09:58:16 +0200
Message-ID: <00ea01d9fb4f$86ed7f40$94c87dc0$@samsung.com> (raw)
In-Reply-To: <AS8P250MB07448E7472438534F9F51B348FC9A@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM>
Oops, you're absolutely right. I can't believe I missed ff_bsf_get_packet_ref.
My apologies for the false alarm.
It's a lesson for me to be more attentive.
Dawid
> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
> Andreas Rheinhardt
> Sent: piątek, 6 października 2023 15:11
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [PATCH v1] avcodec/vp9_superframe_split_bsf: Fix
> for possible null pointer dereference
>
> Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics:
> >
> > Pointer ctx->priv_data->buffer_pkt->data, that can have only NULL value
> (checked at vp9_superframe_split_bsf.c:48), is dereferenced at
> vp9_superframe_split_bsf.c:57.
> >
>
> The rationale for a patch should be included in the commit message and not be
> sent as a reply to the actual patch.
>
> The warning is nonsense and you are breaking the whole BSF with this patch. It is
> perfectly normal for buffer_pkt->data to be NULL at line 48 and to be != NULL at
> line 57: There is a ff_bsf_get_packet_ref() in between which fills the packet.
>
> - Andreas
>
> >
> >> -----Original Message-----
> >> From: Dawid Kozinski <d.kozinski@samsung.com>
> >> Sent: piątek, 6 października 2023 13:02
> >> To: d.frankiewic@samsung.com; ffmpeg-devel@ffmpeg.org
> >> Cc: Dawid Kozinski <d.kozinski@samsung.com>
> >> Subject: [PATCH v1] avcodec/vp9_superframe_split_bsf: Fix for
> >> possible null pointer dereference
> >>
> >> Signed-off-by: Dawid Kozinski <d.kozinski@samsung.com>
> >> ---
> >> libavcodec/vp9_superframe_split_bsf.c | 2 +-
> >> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/libavcodec/vp9_superframe_split_bsf.c
> >> b/libavcodec/vp9_superframe_split_bsf.c
> >> index cddd48119c..4f94afc6d9 100644
> >> --- a/libavcodec/vp9_superframe_split_bsf.c
> >> +++ b/libavcodec/vp9_superframe_split_bsf.c
> >> @@ -45,7 +45,7 @@ static int vp9_superframe_split_filter(AVBSFContext
> >> *ctx, AVPacket *out)
> >> int i, j, ret, marker;
> >> int is_superframe = !!s->buffer_pkt->data;
> >>
> >> - if (!s->buffer_pkt->data) {
> >> + if (s->buffer_pkt->data) {
> >> ret = ff_bsf_get_packet_ref(ctx, s->buffer_pkt);
> >> if (ret < 0)
> >> return ret;
> >> --
> >> 2.25.1
> >
> >
>
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> https://protect2.fireeye.com/v1/url?k=17d2741b-76af9c5c-17d3ff54-
> 74fe485fff30-c67cc2f5726cb1a6&q=1&e=84d99260-3508-4d83-bca4-
> 3e475cf427c4&u=https%3A%2F%2Fffmpeg.org%2Fmailman%2Flistinfo%2Fffmp
> eg-devel
>
> To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org
> with subject "unsubscribe".
_______________________________________________
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".
prev parent reply other threads:[~2023-10-10 7:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20231006110146eucas1p19823b45501652d9049aba8c393ab5266@eucas1p1.samsung.com>
2023-10-06 11:01 ` Dawid Kozinski
2023-10-06 11:13 ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics
2023-10-06 13:10 ` Andreas Rheinhardt
2023-10-10 7:58 ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics [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='00ea01d9fb4f$86ed7f40$94c87dc0$@samsung.com' \
--to=d.kozinski@samsung.com \
--cc=ffmpeg-devel@ffmpeg.org \
/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