mbox

[nf-next,0/9] netfilter updates for -next

Message ID 20240129145807.8773-1-fw@strlen.de
State Accepted
Headers show

Pull-request

https://git.kernel.org/pub/scm/linux/kernel/git/netfilter/nf-next.git tags/nf-next-24-01-29

Message

Florian Westphal Jan. 29, 2024, 2:57 p.m. UTC
Hello,

This batch contains updates for your *next* tree.

First three changes, from Phil Sutter, allow userspace to define
a table that is exclusively owned by a daemon (via netlink socket
aliveness) without auto-removing this table when the userspace program
exits.  Such table gets marked as orphaned and a restarting management
daemon may re-attach/reassume ownership.

Next patch, from Pablo, passes already-validated flags variable around
rather than having called code re-fetch it from netlnik message.

Patches 5 and 6 update ipvs and nf_conncount to use the recently
introduced KMEM_CACHE() macro.

Last three patches, from myself, tweak kconfig logic a little to
permit a kernel configuration that can run iptables-over-nftables
but not classic (setsockopt) iptables.

Such builds lack the builtin-filter/mangle/raw/nat/security tables,
the set/getsockopt interface and the "old blob format"
interpreter/traverser.  For now, this is 'oldconfig friendly', users
need to manually deselect existing config options for this.

The following changes since commit 723de3ebef03bc14bd72531f00f9094337654009:

  net: free altname using an RCU callback (2024-01-29 14:40:38 +0000)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/netfilter/nf-next.git tags/nf-next-24-01-29

for you to fetch changes up to 7ad269787b6615ca56bb161063331991fce51abf:

  netfilter: ebtables: allow xtables-nft only builds (2024-01-29 15:43:21 +0100)

----------------------------------------------------------------
nf-next pr 2024-01-29

----------------------------------------------------------------
Florian Westphal (3):
      netfilter: arptables: allow xtables-nft only builds
      netfilter: xtables: allow xtables-nft only builds
      netfilter: ebtables: allow xtables-nft only builds

Kunwu Chan (2):
      netfilter: nf_conncount: Use KMEM_CACHE instead of kmem_cache_create()
      ipvs: Simplify the allocation of ip_vs_conn slab caches

Pablo Neira Ayuso (1):
      netfilter: nf_tables: pass flags to set backend selection routine

Phil Sutter (3):
      netfilter: uapi: Document NFT_TABLE_F_OWNER flag
      netfilter: nf_tables: Introduce NFT_TABLE_F_PERSIST
      netfilter: nf_tables: Implement table adoption support

 include/net/netfilter/nf_tables.h        |  6 +++++
 include/uapi/linux/netfilter/nf_tables.h |  6 ++++-
 net/bridge/netfilter/Kconfig             |  7 ++++++
 net/bridge/netfilter/Makefile            |  2 +-
 net/ipv4/netfilter/Kconfig               | 43 +++++++++++++++++++-------------
 net/ipv4/netfilter/Makefile              |  2 +-
 net/ipv6/netfilter/Kconfig               | 20 ++++++++++-----
 net/ipv6/netfilter/Makefile              |  2 +-
 net/netfilter/Kconfig                    | 12 ++++-----
 net/netfilter/ipvs/ip_vs_conn.c          |  4 +--
 net/netfilter/nf_conncount.c             |  8 ++----
 net/netfilter/nf_tables_api.c            | 35 ++++++++++++++++++--------
 12 files changed, 94 insertions(+), 53 deletions(-)

Comments

Jakub Kicinski Jan. 31, 2024, 2:37 a.m. UTC | #1
On Mon, 29 Jan 2024 15:57:50 +0100 Florian Westphal wrote:
> Hello,
> 
> This batch contains updates for your *next* tree.

The nf-next in the subject is a typo, right? It's for net-next?
Looks like it but better safe than sorry :)
Pablo Neira Ayuso Jan. 31, 2024, 8:47 a.m. UTC | #2
On Tue, Jan 30, 2024 at 06:37:29PM -0800, Jakub Kicinski wrote:
> On Mon, 29 Jan 2024 15:57:50 +0100 Florian Westphal wrote:
> > Hello,
> > 
> > This batch contains updates for your *next* tree.
> 
> The nf-next in the subject is a typo, right? It's for net-next?
> Looks like it but better safe than sorry :)

Yes, I confirm this is net-next material.
Florian Westphal Jan. 31, 2024, 11:22 a.m. UTC | #3
Jakub Kicinski <kuba@kernel.org> wrote:
> On Mon, 29 Jan 2024 15:57:50 +0100 Florian Westphal wrote:
> > Hello,
> > 
> > This batch contains updates for your *next* tree.
> 
> The nf-next in the subject is a typo, right? It's for net-next?
> Looks like it but better safe than sorry :)

Yes, should've been *net-next*,  used to typing 'nf-next'...

I've updated local plumbing to refuse sending if cover letter
is absent or lacks PATCH net(-next) in subject, so this should
not happen again.