All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Dillinger <miked@softtalker.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter@vger.kernel.org
Subject: Re: nftables: Strange Error When Adding Element to Named Set
Date: Sun, 31 May 2020 10:18:29 -0700	[thread overview]
Message-ID: <10558cf4-649d-2075-857e-cf9abf580de8@softtalker.com> (raw)
In-Reply-To: <20200508160132.GA2278@salvia>

> *From:* Pablo Neira Ayuso [mailto:pablo@netfilter.org]
> *To:* Mike Dillinger <miked@softtalker.com>
> *Cc:* netfilter@vger.kernel.org
> *Date:* Friday, May 8, 2020, 9:01 AM PDT
> *Subject:* nftables: Strange Error When Adding Element to Named Set
>
> Please, make sure your Linux kernel version is >= 5.6.7 or manually
> cherry-pick this fix which was included starting that version.
> Versions from 5.6.0 to 5.6.6 include this problem you describe.
>
> See https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.6.7
>
> Author: Stefano Brivio <sbrivio@redhat.com>
> Date:   Wed Apr 1 17:14:38 2020 +0200
>
>      netfilter: nft_set_rbtree: Drop spurious condition for overlap detection on insertion
>      
>      commit 72239f2795fab9a58633bd0399698ff7581534a3 upstream.

If I am reading the output of uname correctly, I am using 5.6.14 which should qualify:
$ uname -a
Linux rockenfield 5.6.0-2-amd64 #1 SMP Debian 5.6.14-1 (2020-05-23) x86_64 GNU/Linux

...yet, the problem still persists:
$ nft add element ip filter blacklist4-ip-12h { a.b.c.d }
Error: Could not process rule: File exists
add element ip filter blacklist4-ip-12h { a.b.c.d }
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

To confirm, everything works fine with 5.5.x kernels.  Please advise next steps with respect to 5.6.7+ kernels.

Thanks,
-MikeD

  parent reply	other threads:[~2020-05-31 17:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-08 14:06 nftables: Strange Error When Adding Element to Named Set Mike Dillinger
2020-05-08 16:01 ` Pablo Neira Ayuso
2020-05-08 17:13   ` Mike Dillinger
2020-05-31 17:18   ` Mike Dillinger [this message]
2020-06-01 12:41     ` Pablo Neira Ayuso
2020-06-01 14:58       ` Mike Dillinger
2020-06-01 15:48         ` Stefano Brivio
2020-06-01 16:13           ` Mike Dillinger
2020-06-01 16:07         ` Mike Dillinger
2020-06-02 13:28           ` Mike Dillinger
2020-06-02 14:25             ` Stefano Brivio
2020-06-02 16:38               ` Stefano Brivio
2020-06-02 19:58                 ` Mike Dillinger
2020-06-06 13:10                   ` meta day not working pauloric
2020-06-06 14:37                     ` Florian Westphal
2020-06-06 15:06                       ` pauloric

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=10558cf4-649d-2075-857e-cf9abf580de8@softtalker.com \
    --to=miked@softtalker.com \
    --cc=netfilter@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 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.