Netfilter fixes for net
Subsystems (3)
Pablo Neira Ayuso
maintainercover Netfilter fixes for net
Hi David,
The following patchset contains Netfilter fixes for net, they are:
1) Fix spurious overlap condition in the rbtree tree, from Stefano Brivio.
2) Fix possible uninitialized pointer dereference in nft_lookup.
3) IDLETIMER v1 target matches the Android layout, from Maciej Zenczykowski.
4) Dangling pointer in nf_tables_set_alloc_name, from Eric Dumazet.
5) Fix RCU warning splat in ipset find_set_type(), from Amol Grover.
6) Report EOPNOTSUPP on unsupported set flags and object types in sets.
7) Add NFT_SET_CONCAT flag to provide consistent error reporting when users defines set with ranges in concatenations in old kernels.
You can pull these changes from:
git://git.kernel.org/pub/scm/linux/kernel/git/pablo/nf.git
Thank you.
----------------------------------------------------------------
The following changes since commit 0452800f6db4ed0a42ffb15867c0acfd68829f6a:
net: dsa: mt7530: fix null pointer dereferencing in port5 setup (2020-04-03 16:10:32 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/pablo/nf.git HEAD
for you to fetch changes up to ef516e8625ddea90b3a0313f3a0b0baa83db7ac2:
netfilter: nf_tables: reintroduce the NFT_SET_CONCAT flag (2020-04-07 18:23:04 +0200)
----------------------------------------------------------------
Amol Grover (1):
netfilter: ipset: Pass lockdep expression to RCU lists
Eric Dumazet (1):
netfilter: nf_tables: do not leave dangling pointer in nf_tables_set_alloc_name
Maciej Żenczykowski (1):
netfilter: xt_IDLETIMER: target v1 - match Android layout
Pablo Neira Ayuso (3):
netfilter: nf_tables: do not update stateful expressions if lookup is inverted
netfilter: nf_tables: report EOPNOTSUPP on unsupported flags/object type
netfilter: nf_tables: reintroduce the NFT_SET_CONCAT flag
Stefano Brivio (1):
netfilter: nft_set_rbtree: Drop spurious condition for overlap detection on insertion
include/net/netfilter/nf_tables.h | 2 +- include/uapi/linux/netfilter/nf_tables.h | 2 ++ include/uapi/linux/netfilter/xt_IDLETIMER.h | 1 + net/netfilter/ipset/ip_set_core.c | 3 ++- net/netfilter/nf_tables_api.c | 7 ++++--- net/netfilter/nft_lookup.c | 12 +++++++----- net/netfilter/nft_set_bitmap.c | 1 - net/netfilter/nft_set_rbtree.c | 23 +++++++++++------------ net/netfilter/xt_IDLETIMER.c | 3 +++ 9 files changed, 31 insertions(+), 23 deletions(-)
Pablo Neira Ayuso
maintainerPATCH 1/7 netfilter: nft_set_rbtree: Drop spurious condition for overlap detection on insertion
From: Stefano Brivio <[email protected]>
Case a1. for overlap detection in __nft_rbtree_insert() is not a valid
one: start-after-start is not needed to detect any type of interval overlap and it actually results in a false positive if, while descending the tree, this is the only step we hit after starting from the root.
This introduced a regression, as reported by Pablo, in Python tests cases ip/ip.t and ip/numgen.t:
ip/ip.t: ERROR: line 124: add rule ip test-ip4 input ip hdrlength vmap { 0-4 : drop, 5 : accept, 6 : continue } counter: This rule should not have failed. ip/numgen.t: ERROR: line 7: add rule ip test-ip4 pre dnat to numgen inc mod 10 map { 0-5 : 192.168.10.100, 6-9 : 192.168.20.200}: This rule should not have failed.
Drop case a1. and renumber others, so that they are a bit clearer. In order for these diagrams to be readily understandable, a bigger rework is probably needed, such as an ASCII art of the actual rbtree (instead of a flattened version).
Shell script test sets/0044interval_overlap_0 should cover all possible cases for false negatives, so I consider that test case still sufficient after this change.
v2: Fix comments for cases a3. and b3.
--- net/netfilter/nft_set_rbtree.c | 23 +++++++++++------------ 1 file changed, 11 insertions(+), 12 deletions(-)
net/netfilter/nft_set_rbtree.c +11 -12
@@ -218,27 +218,26 @@ static int __nft_rbtree_insert(const struct net *net, const struct nft_set *set,/* Detect overlaps as we descend the tree. Set the flag in these cases: * -* a1. |__ _ _? >|__ _ _ (insert start after existing start) -* a2. _ _ __>| ?_ _ __| (insert end before existing end) -* a3. _ _ ___| ?_ _ _>| (insert end after existing end) -* a4. >|__ _ _ _ _ __| (insert start before existing end) +* a1. _ _ __>| ?_ _ __| (insert end before existing end) +* a2. _ _ ___| ?_ _ _>| (insert end after existing end) +* a3. _ _ ___? >|_ _ __| (insert start before existing end) * * and clear it later on, as we eventually reach the points indicated by * '?' above, in the cases described below. We'll always meet these * later, locally, due to tree ordering, and overlaps for the intervals * that are the closest together are always evaluated last. * -* b1. |__ _ _! >|__ _ _ (insert start after existing end) -* b2. _ _ __>| !_ _ __| (insert end before existing start) -* b3. !_____>| (insert end after existing start) +* b1. _ _ __>| !_ _ __| (insert end before existing start) +* b2. _ _ ___| !_ _ _>| (insert end after existing start) +* b3. _ _ ___! >|_ _ __| (insert start after existing end) * -* Case a4. resolves to b1.: +* Case a3. resolves to b3.: * - if the inserted start element is the leftmost, because the '0' * element in the tree serves as end element * - otherwise, if an existing end is found. Note that end elements are * always inserted after corresponding start elements. * -* For a new, rightmost pair of elements, we'll hit cases b1. and b3., +* For a new, rightmost pair of elements, we'll hit cases b3. and b2., * in that order. * * The flag is also cleared in two special cases:
@@ -262,9 +261,9 @@ static int __nft_rbtree_insert(const struct net *net, const struct nft_set *set, p = &parent->rb_left;if (nft_rbtree_interval_start (new)) { - overlap =nft_rbtree_interval_start (rbe) && -nft_set_elem_active (&rbe->ext, - genmask); +if (nft_rbtree_interval_end (rbe) && +nft_set_elem_active (&rbe->ext, genmask)) + overlap = false; }else { overlap =nft_rbtree_interval_end (rbe) && nft_set_elem_active(&rbe->ext,
Signature · 1 line
2.11.0
Pablo Neira Ayuso
maintainerPATCH 2/7 netfilter: nf_tables: do not update stateful expressions if lookup is inverted
In reply to Pablo Neira AyusoInitialize set lookup matching element to NULL. Otherwise, the NFT_LOOKUP_F_INV flag reverses the matching logic and it leads to deference an uninitialized pointer to the matching element. Make sure element data area and stateful expression are accessed if there is a matching set element.
This patch undoes 24791b9aa1ab ("netfilter: nft_set_bitmap: initialize set element extension in lookups") which is not required anymore.
--- include/net/netfilter/nf_tables.h | 2 +- net/netfilter/nft_lookup.c | 12 +++++++----- net/netfilter/nft_set_bitmap.c | 1 - 3 files changed, 8 insertions(+), 7 deletions(-)
include/net/netfilter/nf_tables.h +1 -1
@@ -901,7 +901,7 @@ static inline void nft_set_elem_update_expr(const struct nft_set_ext *ext, {struct nft_expr *expr; -if (nft_set_ext_exists (ext,NFT_SET_EXT_EXPR )) { +if (__nft_set_ext_exists (ext,NFT_SET_EXT_EXPR )) { expr =nft_set_ext_expr (ext); expr->ops->eval (expr, regs, pkt); }
net/netfilter/nft_lookup.c +7 -5
@@ -29,7 +29,7 @@ void nft_lookup_eval(const struct nft_expr *expr, {const struct nft_lookup *priv =nft_expr_priv (expr);const struct nft_set *set = priv->set; -const struct nft_set_ext *ext; +const struct nft_set_ext *ext =NULL ;bool found; found = set->ops->lookup(nft_net(pkt), set, ®s->data[priv->sreg],
@@ -39,11 +39,13 @@ void nft_lookup_eval(const struct nft_expr *expr,return ; } -if (set->flags &NFT_SET_MAP ) -nft_data_copy (®s->data[priv->dreg], -nft_set_ext_data (ext), set->dlen); +if (ext) { +if (set->flags &NFT_SET_MAP ) +nft_data_copy (®s->data[priv->dreg], +nft_set_ext_data (ext), set->dlen); -nft_set_elem_update_expr (ext, regs, pkt); +nft_set_elem_update_expr (ext, regs, pkt); + } }static const struct nla_policy nft_lookup_policy[NFTA_LOOKUP_MAX +1 ] = {
net/netfilter/nft_set_bitmap.c +0 -1
@@ -81,7 +81,6 @@ static bool nft_bitmap_lookup(const struct net *net, const struct nft_set *set,u32 idx, off;nft_bitmap_location (set, key, &idx, &off); - *ext =NULL ;return nft_bitmap_active (priv->bitmap, idx, off, genmask); }
Signature · 1 line
2.11.0
Pablo Neira Ayuso
maintainerPATCH 3/7 netfilter: xt_IDLETIMER: target v1 - match Android layout
In reply to Pablo Neira AyusoFrom: Maciej Żenczykowski <[email protected]>
Android has long had an extension to IDLETIMER to send netlink messages to userspace, see:
https://android.googlesource.com/kernel/common/+/refs/heads/android-mainline/include/uapi/linux/netfilter/xt_IDLETIMER.h#42
Note: this is idletimer target rev 1, there is no rev 0 in the Android common kernel sources, see registration at:
https://android.googlesource.com/kernel/common/+/refs/heads/android-mainline/net/netfilter/xt_IDLETIMER.c#483
When we compare that to upstream's new idletimer target rev 1:
https://git.kernel.org/pub/scm/linux/kernel/git/pablo/nf-next.git/tree/include/uapi/linux/netfilter/xt_IDLETIMER.h#n46
We immediately notice that these two rev 1 structs are the same size and layout, and that while timer_type and send_nl_msg are differently named and serve a different purpose, they're at the same offset.
This makes them impossible to tell apart - and thus one cannot know in a mixed Android/vanilla environment whether one means timer_type or send_nl_msg.
Since this is iptables/netfilter uapi it introduces a problem between iptables (vanilla vs Android) userspace and kernel (vanilla vs Android) if the two don't match each other.
Additionally when at some point in the future Android picks up 5.7+ it's not at all clear how to resolve the resulting merge conflict.
Furthermore, since upgrading the kernel on old Android phones is pretty much impossible there does not seem to be an easy way out of this predicament.
The only thing I've been able to come up with is some super disgusting kernel version >= 5.7 check in the iptables binary to flip between different struct layouts.
By adding a dummy field to the vanilla Linux kernel header file we can force the two structs to be compatible with each other.
Long term I think I would like to deprecate send_nl_msg out of Android entirely, but I haven't quite been able to figure out exactly how we depend on it. It seems to be very similar to sysfs notifications but with some extra info.
Currently it's actually always enabled whenever Android uses the IDLETIMER target, so we could also probably entirely remove it from the uapi in favour of just always enabling it, but again we can't upgrade old kernels already in the field.
(Also note that this doesn't change the structure's size, as it is simply fitting into the pre-existing padding, and that since 5.7 hasn't been released yet, there's still time to make this uapi visible change)
--- include/uapi/linux/netfilter/xt_IDLETIMER.h | 1 + net/netfilter/xt_IDLETIMER.c | 3 +++ 2 files changed, 4 insertions(+)
include/uapi/linux/netfilter/xt_IDLETIMER.h +1 -0
@@ -48,6 +48,7 @@ struct idletimer_tg_info_v1 {char label[MAX_IDLETIMER_LABEL_SIZE ]; +__u8 send_nl_msg;/* unused: for compatibility with Android */ __u8 timer_type;/* for kernel module internal use only */
net/netfilter/xt_IDLETIMER.c +3 -0
@@ -346,6 +346,9 @@ static int idletimer_tg_checkentry_v1(const struct xt_tgchk_param *par)pr_debug ("checkentry targinfo%s\n" , info->label); +if (info->send_nl_msg) +return -EOPNOTSUPP ; + ret =idletimer_tg_helper ((struct idletimer_tg_info *)info);if (ret <0 ) {
Signature · 1 line
2.11.0
Pablo Neira Ayuso
maintainerPATCH 4/7 netfilter: nf_tables: do not leave dangling pointer in nf_tables_set_alloc_name
In reply to Pablo Neira AyusoFrom: Eric Dumazet <[email protected]>
If nf_tables_set_alloc_name() frees set->name, we better clear set->name to avoid a future use-after-free or invalid-free.
BUG: KASAN: double-free or invalid-free in nf_tables_newset+0x1ed6/0x2560 net/netfilter/nf_tables_api.c:4148 CPU: 0 PID: 28233 Comm: syz-executor.0 Not tainted 5.6.0-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x188/0x20d lib/dump_stack.c:118 print_address_description.constprop.0.cold+0xd3/0x315 mm/kasan/report.c:374 kasan_report_invalid_free+0x61/0xa0 mm/kasan/report.c:468 __kasan_slab_free+0x129/0x140 mm/kasan/common.c:455 __cache_free mm/slab.c:3426 [inline] kfree+0x109/0x2b0 mm/slab.c:3757 nf_tables_newset+0x1ed6/0x2560 net/netfilter/nf_tables_api.c:4148 nfnetlink_rcv_batch+0x83a/0x1610 net/netfilter/nfnetlink.c:433 nfnetlink_rcv_skb_batch net/netfilter/nfnetlink.c:543 [inline] nfnetlink_rcv+0x3af/0x420 net/netfilter/nfnetlink.c:561 netlink_unicast_kernel net/netlink/af_netlink.c:1303 [inline] netlink_unicast+0x537/0x740 net/netlink/af_netlink.c:1329 netlink_sendmsg+0x882/0xe10 net/netlink/af_netlink.c:1918 sock_sendmsg_nosec net/socket.c:652 [inline] sock_sendmsg+0xcf/0x120 net/socket.c:672 ____sys_sendmsg+0x6b9/0x7d0 net/socket.c:2345 ___sys_sendmsg+0x100/0x170 net/socket.c:2399 __sys_sendmsg+0xec/0x1b0 net/socket.c:2432 do_syscall_64+0xf6/0x7d0 arch/x86/entry/common.c:294 entry_SYSCALL_64_after_hwframe+0x49/0xbe RIP: 0033:0x45c849 Code: ad b6 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 0f 83 7b b6 fb ff c3 66 2e 0f 1f 84 00 00 00 00 RSP: 002b:00007fe5ca21dc78 EFLAGS: 00000246 ORIG_RAX: 000000000000002e RAX: ffffffffffffffda RBX: 00007fe5ca21e6d4 RCX: 000000000045c849 RDX: 0000000000000000 RSI: 0000000020000c40 RDI: 0000000000000003 RBP: 000000000076bf00 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 00000000ffffffff R13: 000000000000095b R14: 00000000004cc0e9 R15: 000000000076bf0c Allocated by task 28233: save_stack+0x1b/0x80 mm/kasan/common.c:72 set_track mm/kasan/common.c:80 [inline] __kasan_kmalloc mm/kasan/common.c:515 [inline] __kasan_kmalloc.constprop.0+0xbf/0xd0 mm/kasan/common.c:488 __do_kmalloc mm/slab.c:3656 [inline] __kmalloc_track_caller+0x159/0x790 mm/slab.c:3671 kvasprintf+0xb5/0x150 lib/kasprintf.c:25 kasprintf+0xbb/0xf0 lib/kasprintf.c:59 nf_tables_set_alloc_name net/netfilter/nf_tables_api.c:3536 [inline] nf_tables_newset+0x1543/0x2560 net/netfilter/nf_tables_api.c:4088 nfnetlink_rcv_batch+0x83a/0x1610 net/netfilter/nfnetlink.c:433 nfnetlink_rcv_skb_batch net/netfilter/nfnetlink.c:543 [inline] nfnetlink_rcv+0x3af/0x420 net/netfilter/nfnetlink.c:561 netlink_unicast_kernel net/netlink/af_netlink.c:1303 [inline] netlink_unicast+0x537/0x740 net/netlink/af_netlink.c:1329 netlink_sendmsg+0x882/0xe10 net/netlink/af_netlink.c:1918 sock_sendmsg_nosec net/socket.c:652 [inline] sock_sendmsg+0xcf/0x120 net/socket.c:672 ____sys_sendmsg+0x6b9/0x7d0 net/socket.c:2345 ___sys_sendmsg+0x100/0x170 net/socket.c:2399 __sys_sendmsg+0xec/0x1b0 net/socket.c:2432 do_syscall_64+0xf6/0x7d0 arch/x86/entry/common.c:294 entry_SYSCALL_64_after_hwframe+0x49/0xbe Freed by task 28233: save_stack+0x1b/0x80 mm/kasan/common.c:72 set_track mm/kasan/common.c:80 [inline] kasan_set_free_info mm/kasan/common.c:337 [inline] __kasan_slab_free+0xf7/0x140 mm/kasan/common.c:476 __cache_free mm/slab.c:3426 [inline] kfree+0x109/0x2b0 mm/slab.c:3757 nf_tables_set_alloc_name net/netfilter/nf_tables_api.c:3544 [inline] nf_tables_newset+0x1f73/0x2560 net/netfilter/nf_tables_api.c:4088 nfnetlink_rcv_batch+0x83a/0x1610 net/netfilter/nfnetlink.c:433 nfnetlink_rcv_skb_batch net/netfilter/nfnetlink.c:543 [inline] nfnetlink_rcv+0x3af/0x420 net/netfilter/nfnetlink.c:561 netlink_unicast_kernel net/netlink/af_netlink.c:1303 [inline] netlink_unicast+0x537/0x740 net/netlink/af_netlink.c:1329 netlink_sendmsg+0x882/0xe10 net/netlink/af_netlink.c:1918 sock_sendmsg_nosec net/socket.c:652 [inline] sock_sendmsg+0xcf/0x120 net/socket.c:672 ____sys_sendmsg+0x6b9/0x7d0 net/socket.c:2345 ___sys_sendmsg+0x100/0x170 net/socket.c:2399 __sys_sendmsg+0xec/0x1b0 net/socket.c:2432 do_syscall_64+0xf6/0x7d0 arch/x86/entry/common.c:294 entry_SYSCALL_64_after_hwframe+0x49/0xbe The buggy address belongs to the object at ffff8880a6032d00 which belongs to the cache kmalloc-32 of size 32 The buggy address is located 0 bytes inside of 32-byte region [ffff8880a6032d00, ffff8880a6032d20) The buggy address belongs to the page: page:ffffea0002980c80 refcount:1 mapcount:0 mapping:ffff8880aa0001c0 index:0xffff8880a6032fc1 flags: 0xfffe0000000200(slab) raw: 00fffe0000000200 ffffea0002a3be88 ffffea00029b1908 ffff8880aa0001c0 raw: ffff8880a6032fc1 ffff8880a6032000 000000010000003e 0000000000000000 page dumped because: kasan: bad access detected
--- net/netfilter/nf_tables_api.c | 1 + 1 file changed, 1 insertion(+)
net/netfilter/nf_tables_api.c +1 -0
@@ -3542,6 +3542,7 @@ static int nf_tables_set_alloc_name(struct nft_ctx *ctx, struct nft_set *set,continue ;if (!strcmp (set->name, i->name)) {kfree (set->name); + set->name =NULL ;return -ENFILE ; } }
Signature · 1 line
2.11.0
Pablo Neira Ayuso
maintainerPATCH 5/7 netfilter: ipset: Pass lockdep expression to RCU lists
In reply to Pablo Neira AyusoFrom: Amol Grover <[email protected]>
ip_set_type_list is traversed using list_for_each_entry_rcu outside an RCU read-side critical section but under the protection of ip_set_type_mutex.
Hence, add corresponding lockdep expression to silence false-positive warnings, and harden RCU lists.
--- net/netfilter/ipset/ip_set_core.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
net/netfilter/ipset/ip_set_core.c +2 -1
@@ -86,7 +86,8 @@ find_set_type(const char *name, u8 family, u8 revision) {struct ip_set_type *type; -list_for_each_entry_rcu (type, &ip_set_type_list, list) +list_for_each_entry_rcu (type, &ip_set_type_list, list, +lockdep_is_held (&ip_set_type_mutex)) if (STRNCMP(type->name, name) && (type->family == family || type->family == NFPROTO_UNSPEC) &&
Signature · 1 line
2.11.0
Pablo Neira Ayuso
maintainerPATCH 6/7 netfilter: nf_tables: report EOPNOTSUPP on unsupported flags/object type
In reply to Pablo Neira AyusoEINVAL should be used for malformed netlink messages. New userspace utility and old kernels might easily result in EINVAL when exercising new set features, which is misleading.
--- net/netfilter/nf_tables_api.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
net/netfilter/nf_tables_api.c +2 -2
@@ -3963,7 +3963,7 @@ static int nf_tables_newset(struct net *net, struct sock *nlsk,NFT_SET_INTERVAL |NFT_SET_TIMEOUT |NFT_SET_MAP |NFT_SET_EVAL | NFT_SET_OBJECT)) - return -EINVAL; + return -EOPNOTSUPP;/* Only one of these operations is supported */ if ((flags & (NFT_SET_MAP |NFT_SET_OBJECT )) == (NFT_SET_MAP |NFT_SET_OBJECT ))
@@ -4001,7 +4001,7 @@ static int nf_tables_newset(struct net *net, struct sock *nlsk, objtype =ntohl (nla_get_be32 (nla[NFTA_SET_OBJ_TYPE ]));if (objtype ==NFT_OBJECT_UNSPEC || objtype >NFT_OBJECT_MAX ) -return -EINVAL ; +return -EOPNOTSUPP ; }else if (flags &NFT_SET_OBJECT )return -EINVAL ;else
Signature · 1 line
2.11.0
Pablo Neira Ayuso
maintainerPATCH 7/7 netfilter: nf_tables: reintroduce the NFT_SET_CONCAT flag
In reply to Pablo Neira AyusoStefano originally proposed to introduce this flag, users hit EOPNOTSUPP in new binaries with old kernels when defining a set with ranges in a concatenation.
--- include/uapi/linux/netfilter/nf_tables.h | 2 ++ net/netfilter/nf_tables_api.c | 2 +- 2 files changed, 3 insertions(+), 1 deletion(-)
include/uapi/linux/netfilter/nf_tables.h +2 -0
@@ -276,6 +276,7 @@ enum nft_rule_compat_attributes {* @NFT_SET_TIMEOUT: set uses timeouts * @NFT_SET_EVAL: set can be updated from the evaluation path * @NFT_SET_OBJECT: set contains stateful objects +* @NFT_SET_CONCAT: set contains a concatenation */ enum nft_set_flags {NFT_SET_ANONYMOUS =0x1 ,
@@ -285,6 +286,7 @@ enum nft_set_flags {NFT_SET_TIMEOUT =0x10 ,NFT_SET_EVAL =0x20 ,NFT_SET_OBJECT =0x40 , + NFT_SET_CONCAT = 0x80, };/**
net/netfilter/nf_tables_api.c +1 -1
@@ -3962,7 +3962,7 @@ static int nf_tables_newset(struct net *net, struct sock *nlsk,if (flags & ~(NFT_SET_ANONYMOUS |NFT_SET_CONSTANT |NFT_SET_INTERVAL |NFT_SET_TIMEOUT |NFT_SET_MAP |NFT_SET_EVAL | -NFT_SET_OBJECT )) +NFT_SET_OBJECT |NFT_SET_CONCAT ))return -EOPNOTSUPP ;/* Only one of these operations is supported */ if ((flags & (NFT_SET_MAP | NFT_SET_OBJECT)) ==
Signature · 1 line
2.11.0
David Miller
maintainerFrom: Pablo Neira Ayuso <[email protected]>
Date: Wed, 8 Apr 2020 00:29:29 +0200
Quoted 13 lines
The following patchset contains Netfilter fixes for net, they are:
1) Fix spurious overlap condition in the rbtree tree, from Stefano Brivio.
2) Fix possible uninitialized pointer dereference in
nft_lookup.3) IDLETIMER v1 target matches the Android layout, from Maciej Zenczykowski.
4) Dangling pointer in
nf_tables_set_alloc_name, from Eric Dumazet.5) Fix RCU warning splat in ipset
find_set_type(), from Amol Grover.
Quoted 8 lines
6) Report EOPNOTSUPP on unsupported set flags and object types in sets.
7) Add
NFT_SET_CONCATflag to provide consistent error reporting when users defines set with ranges in concatenations in old kernels.You can pull these changes from:
git://git.kernel.org/pub/scm/linux/kernel/git/pablo/nf.git
Pulled, thanks.