From: Eric Sandeen <sandeen@redhat.com>
To: Andreas Dilger <adilger@clusterfs.com>
Cc: "Brian D. Behlendorf" <behlendorf1@llnl.gov>,
tytso@mit.edu, linux-ext4@vger.kernel.org, wartens2@llnl.gov
Subject: Re: e2fsprogs coverity patch <cid-33.diff>
Date: Tue, 29 May 2007 15:56:44 -0500 [thread overview]
Message-ID: <465C938C.3060101@redhat.com> (raw)
In-Reply-To: <20070529205141.GB5181@schatzie.adilger.int>
Andreas Dilger wrote:
> On May 29, 2007 13:49 -0500, Eric Sandeen wrote:
>> Brian D. Behlendorf wrote:
>>> Lawrence Livermore National Labs recently ran the source code
>>> analysis tool Coverity over the e2fsprogs-1.39 source to see
>>> if it would identify any significant bugs. The analysis
>>> turned up 38 mostly minor issues which are enumerated here
>>> with patches. We went through and resolved these issues
>>> but would love to see these mostly minor changes reviewed
>>> and commited upstream.
>> Did cid-34.diff get lost?
>
> I still have it in my "apply atop 1.39-WIP" series, so it appears not
> to have made it into Ted's repo. I'm including the patch again for
> posterity.
Thanks Andreas - near as I can tell, it never made it to the list.
-Eric
next prev parent reply other threads:[~2007-05-29 20:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-10 2:11 e2fsprogs coverity patch <cid-33.diff> Brian D. Behlendorf
2007-05-29 18:49 ` Eric Sandeen
2007-05-29 20:51 ` Andreas Dilger
2007-05-29 20:56 ` Eric Sandeen [this message]
2007-05-29 22:20 ` Theodore Tso
2007-05-29 23:10 ` Andreas Dilger
2007-05-31 15:43 ` Theodore Tso
2007-05-30 2:01 ` Eric Sandeen
2007-05-31 15:31 ` Theodore Tso
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=465C938C.3060101@redhat.com \
--to=sandeen@redhat.com \
--cc=adilger@clusterfs.com \
--cc=behlendorf1@llnl.gov \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=wartens2@llnl.gov \
/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.