Subject: Re: Periodic Coverity Scan

Re: Periodic Coverity Scan

From: Jakub Hrozek <jhrozek_at_redhat.com>
Date: Thu, 6 Nov 2014 10:21:23 +0100

On Mon, Nov 03, 2014 at 09:58:12AM +0000, David Drysdale wrote:
> On Sat, Nov 1, 2014 at 3:05 PM, Jakub Hrozek <jhrozek_at_redhat.com> wrote:
> >
> > On Fri, Sep 19, 2014 at 10:55:46AM +0100, David Drysdale wrote:
> > > On Thu, Sep 18, 2014 at 6:17 PM, Jakub Hrozek <jhrozek_at_redhat.com> wrote:
> > >
> > > > On Thu, Sep 18, 2014 at 12:13:36AM +0200, Daniel Stenberg wrote:
> > > > > On Wed, 17 Sep 2014, Jakub Hrozek wrote:
> > > > >
> > > > > >FWIW, we scan all packages in RHEL with Coverity, but mostly look at
> > > > diffs
> > > > > >between versions -- which already found some bugs. I'm not sure if
> > > > anyone
> > > > > >did a full review of all the messages Coverity would spit out..
> > > > >
> > > > > Oh, this made me realize my daily clang-analyzer job wasn't actually
> > > > running
> > > > > on c-ares lately but I've activated it again now and its reports can be
> > > > seen
> > > > > here:
> > > > >
> > > > > http://c-ares.haxx.se/scans/
> > > >
> > > > cool!
> > > >
> > > > In general my experience is that Coverity and clang sometimes find
> > > > different issues, so it's good to run both.
> > > >
> > > > >
> > > > > It looks like we have small issues to work on.
> > > >
> > > > My take:
> > > >
> > > > 1) Dead store Dead increment ares_init.c:1398
> > > > This seems like a false positive. I wonder if clang would
> > > > be happier if we moved "lenv *= 2;" after the realloc check? But that
> > > > would make the code less readable in my opinion.
> > > >
> > >
> > > I thought that was a true positive, although it indicates a slightly
> > > different bug -- the loop is WHILE_FALSE so the continue statement after
> > > doubling the length won't go round it again. Maybe the loop should be
> > > "while (res != 0);" or somesuch?
> >
> > Sorry for the month-long delay.
> >
> > Yes, that sounds like a better solution..I'll ack (after testing!) a
> > patch if you can prepare one..
> >
> > Do the two small fixes I sent earlier look OK to you?
>
> Your two fixes both look good to me.
>
> I've attached below my attempt at the non-looping loop (I tested by removing the
> search line from my /etc/resolv.conf and temporarily changing the loop to start
> at size 4).

> From 997e1aedacc72623549fd83c7b5f464f6c0fe408 Mon Sep 17 00:00:00 2001
> From: David Drysdale <drysdale_at_google.com>
> Date: Mon, 3 Nov 2014 09:43:59 +0000
> Subject: [PATCH] Continue loop if space for hostname not large enough

Looks good to me and doesn't seem to break anything!

Pushed as a0b24beb9506976160a9cc61fb69b2f9f2d54276
Received on 2014-11-06