From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 0/4] ipset patches for nf-next
Date: Mon, 25 Aug 2014 10:28:16 +0200 [thread overview]
Message-ID: <20140825082816.GA8262@salvia> (raw)
In-Reply-To: <1408902583-22451-1-git-send-email-kadlec@blackhole.kfki.hu>
On Sun, Aug 24, 2014 at 07:49:39PM +0200, Jozsef Kadlecsik wrote:
> Hi Pablo,
>
> Please consider to apply the next series of patches:
>
> - Dan Carpenter reported that the static checker emits a warning
> about integer overflows in ip_set_list_set.c, fixed by me
> - missing-field-initializer warnings resolved, from Mark Rustad
> - In netnet and netportnet hash types the range support for IPv4
> was broken, fixed by Sergey Popovich
> - A smatch warning about IPSET_ATTR_MARKMASK validation is fixed
> by Vytas Dauksa.
>
> You can pull the changes from
>
> git://blackhole.kfki.hu/nf-next master
Pulled. Thanks, Jozsef.
next prev parent reply other threads:[~2014-08-25 8:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-24 17:49 [PATCH 0/4] ipset patches for nf-next Jozsef Kadlecsik
2014-08-24 17:49 ` [PATCH 1/4] netfilter: ipset: Removed invalid IPSET_ATTR_MARKMASK validation Jozsef Kadlecsik
2014-08-24 17:49 ` [PATCH 2/4] netfilter: ipset: netnet,netportnet: Fix value range support for IPv4 Jozsef Kadlecsik
2014-08-24 17:49 ` [PATCH 3/4] netfilter: ipset: Resolve missing-field-initializer warnings Jozsef Kadlecsik
2014-08-24 17:49 ` [PATCH 4/4] netfilter: ipset: Fix warn: integer overflows 'sizeof(*map) + size * set->dsize' Jozsef Kadlecsik
2014-08-25 8:28 ` Pablo Neira Ayuso [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-10-29 15:39 [PATCH 0/4] ipset patches for nf-next Jozsef Kadlecsik
2017-09-11 19:52 Jozsef Kadlecsik
2017-09-18 12:30 ` Pablo Neira Ayuso
2017-09-18 18:31 ` Jozsef Kadlecsik
2012-09-21 20:49 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=20140825082816.GA8262@salvia \
--to=pablo@netfilter.org \
--cc=kadlec@blackhole.kfki.hu \
--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 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.