netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni@redhat.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>, Florian Westphal <fw@strlen.de>
Cc: Eric Woudstra <ericwouds@gmail.com>,
	Nikolay Aleksandrov <razor@blackwall.org>,
	Ido Schimmel <idosch@nvidia.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Simon Horman <horms@kernel.org>,
	Felix Fietkau <nbd@nbd.name>,
	bridge@lists.linux.dev, netdev@vger.kernel.org,
	netfilter-devel@vger.kernel.org
Subject: Re: [PATCH v1 nf] bridge: br_vlan_fill_forward_path_pvid: use br_vlan_group_rcu()
Date: Tue, 7 Oct 2025 14:49:30 +0200	[thread overview]
Message-ID: <2bca842a-0a94-4798-b215-128809956018@redhat.com> (raw)
In-Reply-To: <aOT0jTumQq39V7p2@calendula>

On 10/7/25 1:07 PM, Pablo Neira Ayuso wrote:
> On Tue, Oct 07, 2025 at 12:09:51PM +0200, Florian Westphal wrote:
>> Eric Woudstra <ericwouds@gmail.com> wrote:
>>> Bug: br_vlan_fill_forward_path_pvid uses br_vlan_group() instead of
>>> br_vlan_group_rcu(). Correct this bug.
>>
>> @netdev maintainers:
>>
>> In case you wish to take this via net tree:
>>
>> Reviewed-by: Florian Westphal <fw@strlen.de>
>>
>> Else I will apply this to nf.git and will pass it to -net
>> in next PR.
> 
> There are more fixes cooking, probably we can prepare a batch.

FWIW, I think it makes sense to wait for a NF PR.

Thanks,

Paolo


      reply	other threads:[~2025-10-07 12:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-07  8:15 [PATCH v1 nf] bridge: br_vlan_fill_forward_path_pvid: use br_vlan_group_rcu() Eric Woudstra
2025-10-07 10:00 ` Pablo Neira Ayuso
2025-10-07 10:09 ` Florian Westphal
2025-10-07 11:07   ` Pablo Neira Ayuso
2025-10-07 12:49     ` Paolo Abeni [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=2bca842a-0a94-4798-b215-128809956018@redhat.com \
    --to=pabeni@redhat.com \
    --cc=bridge@lists.linux.dev \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=ericwouds@gmail.com \
    --cc=fw@strlen.de \
    --cc=horms@kernel.org \
    --cc=idosch@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=nbd@nbd.name \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.org \
    --cc=razor@blackwall.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).