From: Florian Westphal <fw@strlen.de>
To: Eric Woudstra <ericwouds@gmail.com>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
Jozsef Kadlecsik <kadlec@netfilter.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>, Shuah Khan <shuah@kernel.org>,
Nikolay Aleksandrov <razor@blackwall.org>,
Vladimir Oltean <olteanv@gmail.com>,
netfilter-devel@vger.kernel.org, netdev@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [RFC PATCH v3 nf-next] selftests: netfilter: Add bridge_fastpath.sh
Date: Sat, 4 Oct 2025 14:19:07 +0200 [thread overview]
Message-ID: <aOEQu2fgvx1GlrAA@strlen.de> (raw)
In-Reply-To: <be179c64-8c14-4f38-bab2-4597afc63341@gmail.com>
Eric Woudstra <ericwouds@gmail.com> wrote:
> Changes in the patchset "conntrack: bridge: add double vlan, pppoe and
> pppoe-in-q" has lead to changes in this script. I'm waiting for that
> patch-set is to be accepted. Then I will send this script without the
> rfc tag.
Can you send this script standalone? You can extend it along with the
feature patches.
> > Its a pre-existing bug, br_vlan_fill_forward_path_pvid uses
> > br_vlan_group() instead of _rcu version.
> >
> > Will you send a patch for this?
> I had this as part of an upcoming patch-set, but I will remove it from
> there and send it as a separate patch. I assume this can go to nf
> instead of nf-next, as it is a bugfix?
Yes, standalone fix for nf, with "Fies" tag pointing at the patch
that introduced this bug.
prev parent reply other threads:[~2025-10-04 12:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-25 18:33 [RFC PATCH v3 nf-next] selftests: netfilter: Add bridge_fastpath.sh Eric Woudstra
2025-09-30 19:19 ` Florian Westphal
2025-10-04 11:01 ` Eric Woudstra
2025-10-04 12:19 ` Florian Westphal [this message]
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=aOEQu2fgvx1GlrAA@strlen.de \
--to=fw@strlen.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=ericwouds@gmail.com \
--cc=horms@kernel.org \
--cc=kadlec@netfilter.org \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.org \
--cc=razor@blackwall.org \
--cc=shuah@kernel.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.