All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Bruce Cran <bruce@cran.org.uk>,
	"fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: Clang static analyzer warnings
Date: Fri, 14 Aug 2015 09:46:21 -0600	[thread overview]
Message-ID: <55CE0D4D.6020103@kernel.dk> (raw)
In-Reply-To: <55C0DEDA.2090306@cran.org.uk>

On 08/04/2015 09:48 AM, Bruce Cran wrote:
> I don't know how many of these are false positives, but I ran clang's
> static analyzer and it found a few potential issues. e.g.:
>
> client.c:1577:3: warning: Use of memory after it is freed
>                  fio_client_dec_jobs_eta(eta, ops->eta);
>                  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> client.c:1579:2: warning: Use of memory after it is freed
>          dprint(FD_NET, "client: requested eta tag %p\n", eta);
>
> I've attached a copy of the build log, which includes the other warnings.

I don't think that's a real issue. I changed the code to make it 
explicit, hopefully that'll help clang as well.


-- 
Jens Axboe



      reply	other threads:[~2015-08-14 15:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-04 15:48 Clang static analyzer warnings Bruce Cran
2015-08-14 15:46 ` Jens Axboe [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=55CE0D4D.6020103@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=bruce@cran.org.uk \
    --cc=fio@vger.kernel.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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.