All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Dave Jones <davej@redhat.com>
Cc: netdev@vger.kernel.org, oliver@8.c.9.b.0.7.4.0.1.0.0.2.ip6.arpa,
	netfilter-devel@vger.kernel.org
Subject: Re: netfilter: ipset: fix incorret comparison in hash_netnet4_data_equal()
Date: Mon, 25 Nov 2013 22:45:11 +0100	[thread overview]
Message-ID: <20131125214511.GA10043@localhost> (raw)
In-Reply-To: <20131114154101.GA22625@redhat.com>

On Thu, Nov 14, 2013 at 10:41:01AM -0500, Dave Jones wrote:
> Both sides of the comparison are the same, looks like a cut-and-paste error.
> 
> Spotted by Coverity.

Applied, thanks Dave.

Please, cc netfilter-devel for netfilter patches next time.

  reply	other threads:[~2013-11-25 21:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-14 15:41 netfilter: ipset: fix incorret comparison in hash_netnet4_data_equal() Dave Jones
2013-11-25 21:45 ` Pablo Neira Ayuso [this message]
2013-12-07 12:23   ` Oliver
2013-12-07 19:53     ` Jozsef Kadlecsik
2013-12-07 22:34       ` Pablo Neira Ayuso
2013-12-08  9:31         ` Jozsef Kadlecsik

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=20131125214511.GA10043@localhost \
    --to=pablo@netfilter.org \
    --cc=davej@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=oliver@8.c.9.b.0.7.4.0.1.0.0.2.ip6.arpa \
    /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.