From: patchwork-bot+netdevbpf@kernel.org
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org, davem@davemloft.net,
netdev@vger.kernel.org, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com
Subject: Re: [PATCH net 1/2] netfilter: nft_set_rbtree: Switch to node list walk for overlap detection
Date: Tue, 24 Jan 2023 06:00:17 +0000 [thread overview]
Message-ID: <167454001754.8616.2198972017309241814.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230123211601.292930-2-pablo@netfilter.org>
Hello:
This series was applied to netdev/net.git (master)
by Pablo Neira Ayuso <pablo@netfilter.org>:
On Mon, 23 Jan 2023 22:16:00 +0100 you wrote:
> ...instead of a tree descent, which became overly complicated in an
> attempt to cover cases where expired or inactive elements would affect
> comparisons with the new element being inserted.
>
> Further, it turned out that it's probably impossible to cover all those
> cases, as inactive nodes might entirely hide subtrees consisting of a
> complete interval plus a node that makes the current insertion not
> overlap.
>
> [...]
Here is the summary with links:
- [net,1/2] netfilter: nft_set_rbtree: Switch to node list walk for overlap detection
https://git.kernel.org/netdev/net/c/c9e6978e2725
- [net,2/2] netfilter: nft_set_rbtree: skip elements in transaction from garbage collection
https://git.kernel.org/netdev/net/c/5d235d6ce75c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-01-24 6:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 21:15 [PATCH net 0/2] Netfilter fixes for net Pablo Neira Ayuso
2023-01-23 21:16 ` [PATCH net 1/2] netfilter: nft_set_rbtree: Switch to node list walk for overlap detection Pablo Neira Ayuso
2023-01-24 6:00 ` patchwork-bot+netdevbpf [this message]
2023-01-23 21:16 ` [PATCH net 2/2] netfilter: nft_set_rbtree: skip elements in transaction from garbage collection Pablo Neira Ayuso
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=167454001754.8616.2198972017309241814.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pabeni@redhat.com \
--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.