netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: pablo@netfilter.org
Cc: netfilter-devel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 00/10] Netfilter/IPVS updates for net-next
Date: Tue, 08 Mar 2016 14:28:49 -0500 (EST)	[thread overview]
Message-ID: <20160308.142849.1605654925313096504.davem@davemloft.net> (raw)
In-Reply-To: <1457431250-3086-1-git-send-email-pablo@netfilter.org>

From: Pablo Neira Ayuso <pablo@netfilter.org>
Date: Tue,  8 Mar 2016 11:00:40 +0100

> The following patchset contains Netfilter updates for your net-next tree,
> they are:
> 
> 1) Remove useless debug message when deleting IPVS service, from
>    Yannick Brosseau.
> 
> 2) Get rid of compilation warning when CONFIG_PROC_FS is unset in
>    several spots of the IPVS code, from Arnd Bergmann.
> 
> 3) Add prandom_u32 support to nft_meta, from Florian Westphal.
> 
> 4) Remove unused variable in xt_osf, from Sudip Mukherjee.
> 
> 5) Don't calculate IP checksum twice from netfilter ipv4 defrag hook
>    since fixing af_packet defragmentation issues, from Joe Stringer.
> 
> 6) On-demand hook registration for iptables from netns. Instead of
>    registering the hooks for every available netns whenever we need
>    one of the support tables, we register this on the specific netns
>    that needs it, patchset from Florian Westphal.
> 
> 7) Add missing port range selection to nf_tables masquerading support.
> 
> BTW, just for the record, there is a typo in the description of
> 5f6c253ebe93b0 ("netfilter: bridge: register hooks only when bridge
> interface is added") that refers to the cluster match as deprecated, but
> it is actually the CLUSTERIP target (which registers hooks
> inconditionally) the one that is scheduled for removal.
> 
> You can pull these changes from:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/pablo/nf-next.git

Pulled, thanks Pablo!

      parent reply	other threads:[~2016-03-08 19:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-08 10:00 [PATCH 00/10] Netfilter/IPVS updates for net-next Pablo Neira Ayuso
2016-03-08 10:00 ` [PATCH 01/10] netfilter: ipvs: Remove noisy debug print from ip_vs_del_service Pablo Neira Ayuso
2016-03-08 10:00 ` [PATCH 02/10] netfilter: ipvs: avoid unused variable warnings Pablo Neira Ayuso
2016-03-08 10:00 ` [PATCH 03/10] netfilter: meta: add PRANDOM support Pablo Neira Ayuso
2016-03-08 10:00 ` [PATCH 04/10] netfilter: xt_osf: remove unused variable Pablo Neira Ayuso
2016-03-08 10:00 ` [PATCH 05/10] netfilter: nf_defrag_ipv4: Drop redundant ip_send_check() Pablo Neira Ayuso
2016-03-08 10:00 ` [PATCH 06/10] netfilter: xtables: prepare for on-demand hook register Pablo Neira Ayuso
2016-03-08 10:00 ` [PATCH 07/10] netfilter: xtables: don't hook tables by default Pablo Neira Ayuso
2016-03-08 10:00 ` [PATCH 08/10] netfilter: bridge: register hooks only when bridge interface is added Pablo Neira Ayuso
2016-03-08 10:00 ` [PATCH 09/10] netfilter: don't call hooks unless needed Pablo Neira Ayuso
2016-03-08 10:00 ` [PATCH 10/10] netfilter: nft_masq: support port range Pablo Neira Ayuso
2016-03-08 19:28 ` David Miller [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=20160308.142849.1605654925313096504.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.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).