From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Laveesh Bansal <laveeshb@laveeshbansal.com>
Cc: Florian Westphal <fw@strlen.de>,
Nikolay Aleksandrov <razor@blackwall.org>,
Ido Schimmel <idosch@nvidia.com>,
syzbot+a8ba738fe2db6b4bb27f@syzkaller.appspotmail.com,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
bridge@lists.linux.dev, netdev@vger.kernel.org
Subject: Re: [PATCH nf-next 0/2] netfilter: bridge: refragment packets with a vlan tag moved by the bridge
Date: Tue, 10 Nov 2026 01:44:10 +0100 [thread overview]
Message-ID: <avJo2nhgnulY776l@chamomile> (raw)
In-Reply-To: <20261109191842.57359-1-laveeshb@laveeshbansal.com>
Hi,
On Mon, Nov 09, 2026 at 11:18:40AM -0800, Laveesh Bansal wrote:
> Fragmented packets are dropped on a vlan filtering bridge with bridge
> conntrack when the protocol of their vlan tag differs from the bridge's
> vlan_protocol, an 802.1Q tag on an 802.1ad bridge for instance. Patch 1
> handles the tag when refragmenting. Patch 2 adds a selftest.
>
> As discussed with Pablo in the first posting
> (https://lore.kernel.org/r/atck-NoWvemxIsF6@chamomile), the
> DEBUG_NET_WARN_ON_ONCE() change went to nf on its own and is now in the net
> tree as 683ff28ab18a. This series is based on that commit and is meant
> for nf-next, which does not have it yet.
>
> Changes since the first posting
> (https://lore.kernel.org/r/20261020000308.37362-1-laveeshb@laveeshbansal.com):
> patch 1 keeps the tag together with the ethernet header instead of in
> separate fields, and the selftest runs its checks even if the kernel had
> warned before.
>
> I used an LLM tool for the analysis, the code and the test runs.
Do you have a usecase for this?
> I tested the series on arm64 and x86_64, with and without KASAN, lockdep
> and kmemleak. The selftest fails without patch 1.
>
> Laveesh Bansal (2):
> netfilter: bridge: refragment packets with a vlan tag moved by the
> bridge
> selftests: netfilter: add bridge conntrack test for vlan protocol
> mismatch
>
> include/linux/netfilter_bridge.h | 4 +-
> net/bridge/netfilter/nf_conntrack_bridge.c | 46 +++-
> .../testing/selftests/net/netfilter/Makefile | 1 +
> .../net/netfilter/bridge_ct_vlan_proto.sh | 198 ++++++++++++++++++
> tools/testing/selftests/net/netfilter/config | 1 +
> 5 files changed, 241 insertions(+), 9 deletions(-)
> create mode 100755 tools/testing/selftests/net/netfilter/bridge_ct_vlan_proto.sh
>
>
> base-commit: 683ff28ab18accb25268741a724645eee839d41a
> --
> 2.43.0
>
next prev parent reply other threads:[~2026-11-10 0:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 19:18 [PATCH nf-next 0/2] netfilter: bridge: refragment packets with a vlan tag moved by the bridge Laveesh Bansal
2026-11-09 19:18 ` [PATCH nf-next 1/2] " Laveesh Bansal
2026-11-09 19:18 ` [PATCH nf-next 2/2] selftests: netfilter: add bridge conntrack test for vlan protocol mismatch Laveesh Bansal
2026-11-10 0:44 ` Pablo Neira Ayuso [this message]
2026-11-10 1:04 ` [PATCH nf-next 0/2] netfilter: bridge: refragment packets with a vlan tag moved by the bridge Laveesh Bansal
2026-11-10 1:08 ` Pablo Neira Ayuso
2026-11-10 1:22 ` Laveesh Bansal
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=avJo2nhgnulY776l@chamomile \
--to=pablo@netfilter.org \
--cc=bridge@lists.linux.dev \
--cc=coreteam@netfilter.org \
--cc=fw@strlen.de \
--cc=idosch@nvidia.com \
--cc=laveeshb@laveeshbansal.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=razor@blackwall.org \
--cc=syzbot+a8ba738fe2db6b4bb27f@syzkaller.appspotmail.com \
/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