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 02:08:26 +0100 [thread overview]
Message-ID: <avJuijtALFuuk7yd@chamomile> (raw)
In-Reply-To: <20261110010450.68995-1-laveeshb@laveeshbansal.com>
On Mon, Nov 09, 2026 at 05:04:50PM -0800, Laveesh Bansal wrote:
> On Tue, Nov 10, 2026 at 01:44:10AM +0100, Pablo Neira Ayuso wrote:
> > Do you have a usecase for this?
>
> I found this through the syzbot report and haven't seen a user report of
> it.
Yes, there is a patch to fix replace the WARN_ON_ONCE() that could be
found. But does it make sense what syzbot is trying in real life?
> This is the follow-up for nf-next we discussed in
> https://lore.kernel.org/r/atck-NoWvemxIsF6@chamomile.
Yes, I remember, thanks for the link.
next prev parent reply other threads:[~2026-11-10 1:08 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 ` [PATCH nf-next 0/2] netfilter: bridge: refragment packets with a vlan tag moved by the bridge Pablo Neira Ayuso
2026-11-10 1:04 ` Laveesh Bansal
2026-11-10 1:08 ` Pablo Neira Ayuso [this message]
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=avJuijtALFuuk7yd@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 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.