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: br_netfilter: disable sabotage_in hook after first suppression
Date: Wed, 01 Feb 2023 05:30:19 +0000 [thread overview]
Message-ID: <167522941969.3755.300708187812071635.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230131133158.4052-2-pablo@netfilter.org>
Hello:
This series was applied to netdev/net.git (master)
by Pablo Neira Ayuso <pablo@netfilter.org>:
On Tue, 31 Jan 2023 14:31:57 +0100 you wrote:
> From: Florian Westphal <fw@strlen.de>
>
> When using a xfrm interface in a bridged setup (the outgoing device is
> bridged), the incoming packets in the xfrm interface are only tracked
> in the outgoing direction.
>
> $ brctl show
> bridge name interfaces
> br_eth1 eth1
>
> [...]
Here is the summary with links:
- [net,1/2] netfilter: br_netfilter: disable sabotage_in hook after first suppression
https://git.kernel.org/netdev/net/c/2b272bb558f1
- [net,2/2] Revert "netfilter: conntrack: fix bug in for_each_sctp_chunk"
https://git.kernel.org/netdev/net/c/bd0e06f0def7
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-02-01 5:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 13:31 [PATCH net 0/2] Netfilter fixes for net Pablo Neira Ayuso
2023-01-31 13:31 ` [PATCH net 1/2] netfilter: br_netfilter: disable sabotage_in hook after first suppression Pablo Neira Ayuso
2023-02-01 5:30 ` patchwork-bot+netdevbpf [this message]
2023-01-31 13:31 ` [PATCH net 2/2] Revert "netfilter: conntrack: fix bug in for_each_sctp_chunk" 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=167522941969.3755.300708187812071635.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.