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
Subject: Re: [PATCH net 1/2] netfilter: nf_tables: disallow non-stateful expression in sets earlier
Date: Fri, 27 May 2022 04:48:33 +0000 [thread overview]
Message-ID: <165362691345.5864.18094210067248775753.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220526205411.315136-2-pablo@netfilter.org>
Hello:
This series was applied to bpf/bpf.git (master)
by Pablo Neira Ayuso <pablo@netfilter.org>:
On Thu, 26 May 2022 22:54:10 +0200 you wrote:
> Since 3e135cd499bf ("netfilter: nft_dynset: dynamic stateful expression
> instantiation"), it is possible to attach stateful expressions to set
> elements.
>
> cd5125d8f518 ("netfilter: nf_tables: split set destruction in deactivate
> and destroy phase") introduces conditional destruction on the object to
> accomodate transaction semantics.
>
> [...]
Here is the summary with links:
- [net,1/2] netfilter: nf_tables: disallow non-stateful expression in sets earlier
https://git.kernel.org/bpf/bpf/c/520778042ccc
- [net,2/2] netfilter: nft_limit: Clone packet limits' cost value
https://git.kernel.org/bpf/bpf/c/558254b0b602
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:[~2022-05-27 4:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-26 20:54 [PATCH net 0/2] Netfilter fixes for net Pablo Neira Ayuso
2022-05-26 20:54 ` [PATCH net 1/2] netfilter: nf_tables: disallow non-stateful expression in sets earlier Pablo Neira Ayuso
2022-05-27 4:48 ` patchwork-bot+netdevbpf [this message]
2022-05-26 20:54 ` [PATCH net 2/2] netfilter: nft_limit: Clone packet limits' cost value 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=165362691345.5864.18094210067248775753.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--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.