From: Nicolas George <george@nsup.org> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Cc: Eslam Samy <eslamsamy226@yahoo.com> Subject: Re: [FFmpeg-devel] [PATCH] avcodec/v4l2_m2m: Fix segmentation fault due to a missing NULL check in v4l2_context.c Date: Tue, 18 Feb 2025 12:27:26 +0100 Message-ID: <Z7RunmOL6eRnp11R@phare.normalesup.org> (raw) In-Reply-To: <20250218112414.142222-1-eslamsamy226@yahoo.com> Thanks for the patch. Eslam Samy via ffmpeg-devel (HE12025-02-18): > --- > libavcodec/v4l2_context.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/libavcodec/v4l2_context.c b/libavcodec/v4l2_context.c > index be1df3785b..ea11a689bc 100644 > --- a/libavcodec/v4l2_context.c > +++ b/libavcodec/v4l2_context.c > @@ -329,7 +329,7 @@ start: > /* if we are trying to get free buffers but none have been queued yet, > * or if no buffers have been allocated yet, no need to raise a warning > */ > - if (timeout == 0) { > + if ((timeout == 0) && (ctx->buffers != NULL)) { This does not match ffmpeg's coding style, the extra parentheses and the != NULL. > if (!ctx->buffers) > return NULL; Can you explain how this hunk makes sense with your change? Regards, -- Nicolas George _______________________________________________ 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-02-18 11:27 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20250218112414.142222-1-eslamsamy226.ref@yahoo.com> 2025-02-18 11:24 ` Eslam Samy via ffmpeg-devel 2025-02-18 11:27 ` Nicolas George [this message] 2025-02-18 11:46 ` Eslam Samy via ffmpeg-devel 2025-02-18 11:56 ` Nicolas George
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=Z7RunmOL6eRnp11R@phare.normalesup.org \ --to=george@nsup.org \ --cc=eslamsamy226@yahoo.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