From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [WIP] False positives on Coverity
Date: Mon, 10 Jun 2024 00:02:27 +0200
Message-ID: <20240609220227.GY2821752@pb2> (raw)
In-Reply-To: <e1ab7d75-bdad-4c64-b3b7-cb4fd54183d1@rothenpieler.org>
[-- Attachment #1.1: Type: text/plain, Size: 2087 bytes --]
On Sun, Jun 09, 2024 at 12:49:57AM +0200, Timo Rothenpieler wrote:
> On 08.06.2024 21:49, Vittorio Giovara wrote:
> > On Sat, Jun 8, 2024 at 6:02 PM Michael Niedermayer <michael@niedermayer.cc>
> > wrote:
> >
> > > On Tue, May 14, 2024 at 01:38:16AM +0200, Michael Niedermayer wrote:
> > > > Hi all
> > > >
> > > > To keep people updated (and as this is not vissible on the ML)
> > > > heres my current list of issues marked as false positives / intentional
> > > in Mai & April 2024
> > > > (in case anyone wants to review, i presume noone wants but just in case)
> > >
> > > updated list as of today:
> > > [...]
> > >
>
> Given the insane amount of them, I'm not a fan of that.
also what i noticed since i work on the issues
sometimes some issues dissappear and others appear (with no explanation and seemingly
no related changes). Some issues contain
multiple occurances, ive seen a very small number of issues where line numbers are
missing. And one that pointed to a file outside FFmpeg.
Mapping CIDs to some other tracker in a long term stable manner would likely be a
painfull experience.
Also the coverity web app shows more or less details about the detected
issue within the source of FFmpeg in an interactive way. That of course would
also change as the
source changes over time, so it would not be available in another issue tracker
that means the duplicated issues would still require one to go to coverity
if one wanted to work on it.
And last but not least coverity isnt intended to be public because it can
find security issues. security issues should be public once they are fixed
and maybe when someone is working on them. But not when the issues are ignored
amongth hundreads of minor and false positive ones for years
So, yes i share your sceptisism about making coverity issues appear in some
other issue tracker
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
It is a danger to trust the dream we wish for rather than
the science we have, -- Dr. Kenneth Brown
[-- 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-06-09 22:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 23:38 Michael Niedermayer
2024-05-14 7:37 ` Tomas Härdin
2024-05-14 11:28 ` Rémi Denis-Courmont
2024-05-15 8:06 ` Tomas Härdin
2024-06-08 16:01 ` Michael Niedermayer
2024-06-08 19:49 ` Vittorio Giovara
2024-06-08 22:49 ` Timo Rothenpieler
2024-06-09 13:10 ` Vittorio Giovara
2024-06-09 22:04 ` Michael Niedermayer
2024-06-10 12:37 ` Vittorio Giovara
2024-06-10 12:40 ` Timo Rothenpieler
2024-06-10 12:45 ` Vittorio Giovara
2024-06-11 15:46 ` Michael Niedermayer
2024-06-09 22:02 ` Michael Niedermayer [this message]
2024-07-11 23:55 ` Michael Niedermayer
2024-07-12 23:20 ` Michael Niedermayer
2024-07-25 14:41 ` Michael Niedermayer
2024-08-12 17:40 ` 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=20240609220227.GY2821752@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