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 0/3] Netfilter fixes for net
Date: Thu, 30 Jun 2022 03:20:13 +0000 [thread overview]
Message-ID: <165655921391.17409.14718173715479167707.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220629171354.208773-1-pablo@netfilter.org>
Hello:
This series was applied to netdev/net.git (master)
by Pablo Neira Ayuso <pablo@netfilter.org>:
On Wed, 29 Jun 2022 19:13:51 +0200 you wrote:
> Hi,
>
> The following patchset contains Netfilter fixes for net:
>
> 1) Restore set counter when one of the CPU loses race to add elements
> to sets.
>
> [...]
Here is the summary with links:
- [net,1/3] netfilter: nft_dynset: restore set element counter when failing to update
https://git.kernel.org/netdev/net/c/05907f10e235
- [net,2/3] netfilter: nf_tables: avoid skb access on nf_stolen
https://git.kernel.org/netdev/net/c/e34b9ed96ce3
- [net,3/3] netfilter: br_netfilter: do not skip all hooks with 0 priority
https://git.kernel.org/netdev/net/c/c2577862eeb0
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-06-30 3:20 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 17:13 [PATCH net 0/3] Netfilter fixes for net Pablo Neira Ayuso
2022-06-29 17:13 ` [PATCH net 1/3] netfilter: nft_dynset: restore set element counter when failing to update Pablo Neira Ayuso
2022-06-29 17:13 ` [PATCH net 2/3] netfilter: nf_tables: avoid skb access on nf_stolen Pablo Neira Ayuso
2022-06-29 17:13 ` [PATCH net 3/3] netfilter: br_netfilter: do not skip all hooks with 0 priority Pablo Neira Ayuso
2022-06-30 3:20 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-08-13 11:36 [PATCH net 0/3] Netfilter fixes for net Florian Westphal
2025-04-03 11:57 Pablo Neira Ayuso
2025-03-06 15:34 Pablo Neira Ayuso
2024-12-11 23:01 Pablo Neira Ayuso
2024-11-14 12:57 Pablo Neira Ayuso
2024-11-14 14:54 ` Paolo Abeni
2024-11-14 15:00 ` Pablo Neira Ayuso
2024-11-14 15:31 ` Paolo Abeni
2024-11-14 18:08 ` Pablo Neira Ayuso
2024-10-09 21:38 Pablo Neira Ayuso
2024-08-22 0:17 Pablo Neira Ayuso
2024-06-11 22:03 Pablo Neira Ayuso
2024-04-18 1:09 Pablo Neira Ayuso
2024-03-21 0:06 Pablo Neira Ayuso
2024-02-29 0:01 Pablo Neira Ayuso
2024-02-14 23:38 Pablo Neira Ayuso
2023-07-26 15:23 [PATCH net 0/3] netfilter " Florian Westphal
2023-06-08 19:57 [PATCH net 0/3] Netfilter " Pablo Neira Ayuso
2023-05-17 12:37 Florian Westphal
2023-05-03 6:32 Pablo Neira Ayuso
2023-03-07 10:04 Pablo Neira Ayuso
2023-03-07 12:57 ` Paolo Abeni
2023-03-07 17:26 ` Jakub Kicinski
2023-03-08 9:34 ` Pablo Neira Ayuso
2023-03-01 22:20 Pablo Neira Ayuso
2023-01-13 16:41 Pablo Neira Ayuso
2023-01-18 3:03 ` Jakub Kicinski
2023-01-11 21:22 Pablo Neira Ayuso
2022-11-22 21:28 Pablo Neira Ayuso
2022-11-09 11:28 Pablo Neira Ayuso
2022-10-12 12:18 [PATCH net 0/3] netfilter " Florian Westphal
2022-07-11 9:33 [PATCH net 0/3] Netfilter " Pablo Neira Ayuso
2022-04-28 14:21 Pablo Neira Ayuso
2022-03-28 8:20 Pablo Neira Ayuso
2022-03-17 20:25 Pablo Neira Ayuso
2022-03-12 22:03 Pablo Neira Ayuso
2022-03-14 22:54 ` Jakub Kicinski
2022-03-14 23:07 ` Florian Westphal
2022-03-14 23:18 ` Jakub Kicinski
2021-12-17 8:53 Pablo Neira Ayuso
2021-06-10 16:54 Pablo Neira Ayuso
2021-02-02 15:21 Pablo Neira Ayuso
2021-02-02 15:25 ` Pablo Neira Ayuso
2021-01-27 13:25 Pablo Neira Ayuso
2021-01-12 22:20 Pablo Neira Ayuso
2021-01-13 4:26 ` Jakub Kicinski
2021-01-03 19:29 Pablo Neira Ayuso
2021-01-04 23:04 ` Jakub Kicinski
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=165655921391.17409.14718173715479167707.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).