From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH 3/3] avformat/img2dec: assert no pipe on ts_from_file Date: Wed, 8 May 2024 22:04:11 +0200 Message-ID: <20240508200411.GH6420@pb2> (raw) In-Reply-To: <GV1P250MB07378E124F34C079939FB5EC8FE52@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM> [-- Attachment #1.1: Type: text/plain, Size: 2449 bytes --] On Wed, May 08, 2024 at 12:16:44PM +0200, Andreas Rheinhardt wrote: > Michael Niedermayer: > > Help coverity with CID500302 Uninitialized scalar variable > > > > Sponsored-by: Sovereign Tech Fund > > Signed-off-by: Michael Niedermayer <michael@niedermayer.cc> > > --- > > libavformat/img2dec.c | 2 ++ > > 1 file changed, 2 insertions(+) > > > > diff --git a/libavformat/img2dec.c b/libavformat/img2dec.c > > index a40675d4341..6220003fb4d 100644 > > --- a/libavformat/img2dec.c > > +++ b/libavformat/img2dec.c > > @@ -25,6 +25,7 @@ > > #define _DEFAULT_SOURCE > > #define _BSD_SOURCE > > #include <sys/stat.h> > > +#include "libavutil/avassert.h" > > #include "libavutil/avstring.h" > > #include "libavutil/log.h" > > #include "libavutil/mem.h" > > @@ -504,6 +505,7 @@ int ff_img_read_packet(AVFormatContext *s1, AVPacket *pkt) > > pkt->flags |= AV_PKT_FLAG_KEY; > > if (s->ts_from_file) { > > struct stat img_stat; > > + av_assert0(!s->is_pipe); > > if (stat(filename, &img_stat)) { > > res = AVERROR(EIO); > > goto fail; > > 1. You seem to refer to 1500302 yes, fixed locally > which I can't even select any more > because it has been dismissed. no, it can be selected, it works here on the 3rd try coverity sometimes ignores selecting issues sometimes it displayes a long list of unrelated issues sometimes it works > 2. Why are you using av_assert0 to help coverity? I dont understand the question > 3. In cases like these it would be important to actually note why this > assert can't be triggered. With a comment like "The ts_from_file option > is not supported by piped input demuxers". its kind of clear from the assert but i added the comment, > 4. I just sent an alternative for this: > https://ffmpeg.org/pipermail/ffmpeg-devel/2024-May/327035.html. I don't > know which one should be preferred or whether the code should be left as-is. I think if somehow ts_from_file and is_pipe are set. Thats a bug in the code its only the combination of flags and AVOptions that prevents this. I think an assert like in my patch makes the code more robust compared to simply not crashing on an inconsistant state thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB The worst form of inequality is to try to make unequal things equal. -- Aristotle [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 195 bytes --] [-- Attachment #2: Type: text/plain, Size: 251 bytes --] _______________________________________________ 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:[~2024-05-08 20:04 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-08 2:39 [FFmpeg-devel] [PATCH 1/3] avcodec/cbs_jpeg: Assert that cbs_jpeg_assemble_fragment() stays within the array Michael Niedermayer 2024-05-08 2:39 ` [FFmpeg-devel] [PATCH 2/3] avformat/sdp: Check before appending ", " Michael Niedermayer 2024-06-07 19:01 ` Michael Niedermayer 2024-05-08 2:39 ` [FFmpeg-devel] [PATCH 3/3] avformat/img2dec: assert no pipe on ts_from_file Michael Niedermayer 2024-05-08 10:16 ` Andreas Rheinhardt 2024-05-08 20:04 ` Michael Niedermayer [this message] 2024-05-08 9:46 ` [FFmpeg-devel] [PATCH 1/3] avcodec/cbs_jpeg: Assert that cbs_jpeg_assemble_fragment() stays within the array Andreas Rheinhardt 2024-05-08 19:49 ` Michael Niedermayer
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=20240508200411.GH6420@pb2 \ --to=michael@niedermayer.cc \ --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