From: Eric Sandeen <sandeen@redhat.com>
To: dsterba@suse.cz, Zach Brown <zab@zabbo.net>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/4] some btrfs-progs coverity fixes
Date: Thu, 16 Oct 2014 08:33:39 -0500 [thread overview]
Message-ID: <543FC933.7050400@redhat.com> (raw)
In-Reply-To: <20141016114612.GD22943@twin.jikos.cz>
On 10/16/14 6:46 AM, David Sterba wrote:
> On Wed, Oct 15, 2014 at 04:14:17PM -0700, Zach Brown wrote:
>> Here's another set of coverity fixes for btrfs-progs against David's
>> integration-20141007 branch.
>
> Thanks, I've fished 2 patches for 3.17, the rest is queued.
>
>> I got tired of adding error checking after a few so I moved on to the
>> other warnings. Maybe we should subscribe linux-btrfs to the reports
>> that coverity can send out?
>
> I'm not sure if this is allowed by the coverity service and I was not
> able to any info about that.
We could, in theory, "invite" the list, and then I suppose we'd get
a confirmation email that 100 people would click on. ;)
Could maybe just email the scan folks and ask.
I'm a little on the fence about immediately broadcasting all defects, though.
I doubt there should be security implications, but ...
I wish scan were better integrated with git, and then something like
"email the author of the commit that introduced a new defect" would
be pretty cool.
-Eric
prev parent reply other threads:[~2014-10-16 13:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-15 23:14 [PATCH 0/4] some btrfs-progs coverity fixes Zach Brown
2014-10-15 23:14 ` [PATCH 1/4] btrfs-progs: check sscanf return code Zach Brown
2014-10-15 23:14 ` [PATCH 2/4] btrfs-progs: check read extent errors when mapping Zach Brown
2014-10-15 23:14 ` [PATCH 3/4] btrfs-progs: fix show super unknown flag output Zach Brown
2014-10-15 23:14 ` [PATCH 4/4] btrfs-progs: fix csum root copy-n-paste error Zach Brown
2014-10-16 10:55 ` David Sterba
2014-10-16 11:46 ` [PATCH 0/4] some btrfs-progs coverity fixes David Sterba
2014-10-16 13:33 ` Eric Sandeen [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=543FC933.7050400@redhat.com \
--to=sandeen@redhat.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=zab@zabbo.net \
/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.