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:56:03 +0100 Message-ID: <Z7R1U8AGY7RIUu13@phare.normalesup.org> (raw) In-Reply-To: <1997891029.1068778.1739879208343@mail.yahoo.com> Eslam Samy via ffmpeg-devel (HE12025-02-18): > Hi Nicolas, @anchor{What is top-posting?} @section What is top-posting? See @url{https://en.wikipedia.org/wiki/Posting_style#Top-posting}. Instead, use trimmed interleaved/inline replies (@url{https://lists.ffmpeg.org/pipermail/ffmpeg-user/2017-April/035849.html, example}). > The logic behind the change I made is explained here: Ticket #9722. I > tried to fix the issue by adding a null check to prevent the > segmentation fault when ctx->buffers is accessed before being > initialized. Can you confirm that your patch really fixes the issue? You need to confirm you have tested two things: (1) the issue does happen with the current code base and (2) the issue no longer happens with the patch. I strongly suggest you neglected (1). > Regarding the coding style, I reviewed the FFmpeg developer > documentation, but I couldn't find any explicit rules on this matter. > However, I completely understand the importance of adhering to > FFmpeg's coding standards, and I would be happy to modify the patch to > align with the style you suggest. @item No unnecessary parentheses, unless it helps readability: For the rest, you are supposed to imitate the existing code. Feel free to propose adding the rule about null and 0 comparisons. 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".
prev parent reply other threads:[~2025-02-18 11:56 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 2025-02-18 11:46 ` Eslam Samy via ffmpeg-devel 2025-02-18 11:56 ` Nicolas George [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=Z7R1U8AGY7RIUu13@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