From: Bart De Schuymer <bdschuym@pandora.be>
To: Jiri Popelka <jpopelka@redhat.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] ebtables: Possible problems found by static analysis of code
Date: Wed, 15 Jun 2011 22:37:09 +0200 [thread overview]
Message-ID: <4DF917F5.9000605@pandora.be> (raw)
In-Reply-To: <4DF738AE.3060306@redhat.com>
Op 14/06/2011 12:32, Jiri Popelka schreef:
> Hello,
>
> we had analyzed the ebtables-v2.0.9-2 code with Coverity.
> Coverity is commercial enterprise level tool for
> static analysis (analysis based only on compiling of sources,
> not based on running of binary) of the code.
>
> As a result I have the following patches that should fix some possible
> problems.
> There's a respective part(s) of the Coverity error log in each patch.
>
Thanks,
I'll have a closer look at them later this week.
cheers,
Bart
--
Bart De Schuymer
www.artinalgorithms.be
next prev parent reply other threads:[~2011-06-15 20:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 10:32 [PATCH] ebtables: Possible problems found by static analysis of code Jiri Popelka
2011-06-15 20:37 ` Bart De Schuymer [this message]
2011-06-23 18:51 ` Bart De Schuymer
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=4DF917F5.9000605@pandora.be \
--to=bdschuym@pandora.be \
--cc=jpopelka@redhat.com \
--cc=netfilter-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).