From: Chris Mason <chris.mason@fusionio.com>
To: Zach Brown <zab@redhat.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
David Sterba <dsterba@suse.cz>, Eric Sandeen <sandeen@redhat.com>
Subject: Re: btrfs-progs pull request for coverity fixes
Date: Wed, 6 Feb 2013 11:36:45 -0500 [thread overview]
Message-ID: <20130206163645.GO20797@shiny> (raw)
In-Reply-To: <20130206004907.GN14246@lenny.home.zabbo.net>
On Tue, Feb 05, 2013 at 05:49:07PM -0700, 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.
Awesome, thanks Zach and Eric. I've got this rebased on top of Dave's
integration pull from today, and I'm doing a bunch of tests.
-chris
next prev parent reply other threads:[~2013-02-06 16:36 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
2013-02-06 15:04 ` Eric Sandeen
2013-02-06 16:36 ` Chris Mason [this message]
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=20130206163645.GO20797@shiny \
--to=chris.mason@fusionio.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox