From: Marton Balint <cus@passwd.hu> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] avcodec/pcm_rechunk_bsf: unref packet before putting a new one in Date: Sat, 9 Apr 2022 20:56:05 +0200 (CEST) Message-ID: <a98e9e23-3d4f-a4b-449-d8ef7349e640@passwd.hu> (raw) In-Reply-To: <20220330105802.GO2829255@pb2> On Wed, 30 Mar 2022, Michael Niedermayer wrote: > On Tue, Mar 29, 2022 at 06:33:06PM -0300, James Almer wrote: >> On 3/29/2022 6:24 PM, Michael Niedermayer wrote: >>> Fixes: memleak >>> Fixes: 45982/clusterfuzz-testcase-minimized-ffmpeg_BSF_PCM_RECHUNK_fuzzer-5562089618407424 >>> >>> Found-by: continuous fuzzing process https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg >>> Signed-off-by: Michael Niedermayer <michael@niedermayer.cc> >>> --- >>> libavcodec/pcm_rechunk_bsf.c | 1 + >>> 1 file changed, 1 insertion(+) >>> >>> diff --git a/libavcodec/pcm_rechunk_bsf.c b/libavcodec/pcm_rechunk_bsf.c >>> index 108d9e90b9..3f43934fe9 100644 >>> --- a/libavcodec/pcm_rechunk_bsf.c >>> +++ b/libavcodec/pcm_rechunk_bsf.c >>> @@ -153,6 +153,7 @@ static int rechunk_filter(AVBSFContext *ctx, AVPacket *pkt) >>> } >>> } >>> + av_packet_unref(s->in_pkt); >> >> This looks to me like it revealed a bug in the code above, which is meant to >> ensure s->in_pkt will be blank at this point. It should be fixed there >> instead. > > IIRC the problem was a input packet with size 0 > the code seems to assume 0 meaning no packet Is that valid here? The docs says that the encoders can generate 0 sized packets if there is side data in them. However - the PCM rechunk BSF using PCM packets - I am not sure this is intentional here. So overall it looks to me that the PCM rechunk BSF should reject 0 sized packets with AVERROR_INVALIDDATA, and the encoder or demuxer which produces the 0 sized packets should be fixed. Regards, Marton > > I can check more explicitly for that after ff_bsf_get_packet_ref() > and unref there, its more code through > > thx > > > [...] > -- > Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB > > Its not that you shouldnt use gotos but rather that you should write > readable code and code with gotos often but not always is less readable > _______________________________________________ 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:[~2022-04-09 18:56 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-29 21:24 Michael Niedermayer 2022-03-29 21:33 ` James Almer 2022-03-30 10:58 ` Michael Niedermayer 2022-04-09 18:56 ` Marton Balint [this message] 2022-04-10 14:14 ` Michael Niedermayer 2022-04-10 14:46 ` James Almer 2022-04-11 16:52 ` Michael Niedermayer 2022-04-11 17:56 ` Andreas Rheinhardt 2022-06-16 23:30 ` Michael Niedermayer 2022-04-10 16:50 ` Marton Balint
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=a98e9e23-3d4f-a4b-449-d8ef7349e640@passwd.hu \ --to=cus@passwd.hu \ --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