All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gene Czarcinski <gene@czarc.net>
To: linux-btrfs@vger.kernel.org
Cc: Zach Brown <zab@redhat.com>, David Sterba <dsterba@suse.cz>,
	Eric Sandeen <sandeen@redhat.com>
Subject: Re: btrfs-progs pull request for coverity fixes
Date: Wed, 06 Feb 2013 09:27:56 -0500	[thread overview]
Message-ID: <5112686C.9050300@czarc.net> (raw)
In-Reply-To: <20130206004907.GN14246@lenny.home.zabbo.net>

On 02/05/2013 07:49 PM, Zach Brown wrote:
> Hi gang,
>
> Eric and I went through the warnings that a Coverity scan raised against
> the reasonably recent btrfs-progs that's in Fedora.  We tried to tackle
> the lowest hanging fruit: these are the most obvious and least risky
> fixes.
>
If you ran your tests against the btrfs-progs in Fedora 18 then your 
tests may not have found problems fixed by the "valgrind" patch on F18.  
This patch is not applied to the current David Sterba's integration 
branches.

If you have the time, it might be useful (my opinion) to run your tests 
against Sterba's integration-02130201 branch ... some of the problems 
may be fixed and other not but you also may find some additional 
problems.  IMO, this branch (or something similar) will be the basis for 
a future v0.20 btrfs-progs ... at least that is what I am using/testing 
with.  There are over 80 commits in this branch over what is the baseis 
for the package in Fedora 18.

Gene

  reply	other threads:[~2013-02-06 14:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-06  0:49 btrfs-progs pull request for coverity fixes Zach Brown
2013-02-06 14:27 ` Gene Czarcinski [this message]
2013-02-06 15:04   ` Eric Sandeen
2013-02-06 16:36 ` Chris Mason
2013-02-06 17:20   ` Zach Brown

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=5112686C.9050300@czarc.net \
    --to=gene@czarc.net \
    --cc=dsterba@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --cc=zab@redhat.com \
    /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.