* Russ Cox ([email protected]) wrote:
> >If this is whats agreed upon I will no longer send patches for
> >such bugs, and mark them as ignore in the coverity system.
> >But I guess it makes also sense to remove unused code, because I
> >am not sure if gcc can figure out to remove it. In this case
> >the generated object file is 10 bytes smaller.
>
> I wasn't necessarily speaking for the group so much as I was interested
> in how coverity was being used and what the rules were.
> Thanks for the info.
guess thats depends on the person looking trough the bugs :)
As far as i know, there are no official rules ( except maybe
to never let gregkh see a false positive :), i just try to
take a look at the coverity reports, and fix whatever I can,
in cleanup cases like this it clearly depends on the maintainer,
what he does with the patch. the coverity guys seem to be pretty
nice in giving accounts away, so you might want to take a look
at this stuff yourself. At the moment about half of the inspected
"bugs" have been marked as invalid or false, to shut coverity up
about clearly defensive programming or false analysis, so i guess
the main part is not to make coverity shut up with a patch, since
marking it as invalid is much less hassle.
Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
