Netdev List
 help / color / mirror / Atom feed
From: Nikolay Aleksandrov <razor@blackwall.org>
To: netdev@vger.kernel.org
Cc: idosch@nvidia.com, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
	bridge@lists.linux.dev
Subject: Re: [PATCH net-next 0/9] net: bridge: vlan: minor cleanups and annotations
Date: Wed, 2 Sep 2026 20:22:07 +0300	[thread overview]
Message-ID: <239e8a53-fb02-4021-8f74-6c232e9c9b6f@blackwall.org> (raw)
In-Reply-To: <20260901120721.747908-1-razor@blackwall.org>

On 01/09/2026 15:07, Nikolay Aleksandrov wrote:
> Hi,
> In preparation for a complete vlan fast-path re-work, this set cleans up
> a few minor things - removing legacy code barriers that don't help,
>                       annotating lockless accesses and using proper helpers.
> No functional changes are intended. Sashiko will find many pre-existing
> problems, none of them are related to this set. I will try to fix
> everything pre-existing separately in -net, there will probably be a few
> critical items. So if there are missed places to annotate, or if there're
> actual functional changes, these obviously should be addressed in this set.
> 
> Thanks,
>   Nik
> 
> Nikolay Aleksandrov (9):
>    net: bridge: vlan: drop legacy memory barriers
>    net: bridge: vlan: annotate lockless pvid use
>    net: bridge: mst: use br_get_pvid helper
>    net: bridge: vlan: annotate lockless vlan flags use
>    net: bridge: vlan: annotate lockless use of private flags
>    net: bridge: vlan: annotate lockless use of num_vlans
>    net: bridge: vlan: annotate lockless use of msti
>    net: bridge: vlan: add missing tinfo.tunnel_id annotations
>    net: bridge: vlan: use br_vlan_get_state to get vlan state
> 
>   net/bridge/br_arp_nd_proxy.c   |  6 ++++--
>   net/bridge/br_mst.c            | 12 ++++++-----
>   net/bridge/br_multicast.c      | 18 ++++++++++------
>   net/bridge/br_netlink.c        | 10 ++++-----
>   net/bridge/br_netlink_tunnel.c | 12 +++++------
>   net/bridge/br_private.h        | 16 ++++++++------
>   net/bridge/br_vlan.c           | 39 +++++++++++++++++-----------------
>   net/bridge/br_vlan_options.c   |  6 ++++--
>   net/bridge/br_vlan_tunnel.c    |  2 +-
>   9 files changed, 67 insertions(+), 54 deletions(-)
> 

Me and Ido had a chat and he commented that patch 09 is far from done, I missed state
accesses outside of br_vlan.c, silly mistake. Anyway, I'll fix it up and post v2.

Cheers,
  Nik

---
pw-bot: cr

      parent reply	other threads:[~2026-09-02 17:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-01 12:07 [PATCH net-next 0/9] net: bridge: vlan: minor cleanups and annotations Nikolay Aleksandrov
2026-09-01 12:07 ` [PATCH net-next 1/9] net: bridge: vlan: drop legacy memory barriers Nikolay Aleksandrov
2026-09-01 12:07 ` [PATCH net-next 2/9] net: bridge: vlan: annotate lockless pvid use Nikolay Aleksandrov
2026-09-01 12:07 ` [PATCH net-next 3/9] net: bridge: mst: use br_get_pvid helper Nikolay Aleksandrov
2026-09-01 12:07 ` [PATCH net-next 4/9] net: bridge: vlan: annotate lockless vlan flags use Nikolay Aleksandrov
2026-09-01 12:07 ` [PATCH net-next 5/9] net: bridge: vlan: annotate lockless use of private flags Nikolay Aleksandrov
2026-09-01 12:07 ` [PATCH net-next 6/9] net: bridge: vlan: annotate lockless use of num_vlans Nikolay Aleksandrov
2026-09-01 12:07 ` [PATCH net-next 7/9] net: bridge: vlan: annotate lockless use of msti Nikolay Aleksandrov
2026-09-01 12:07 ` [PATCH net-next 8/9] net: bridge: vlan: add missing tinfo.tunnel_id annotations Nikolay Aleksandrov
2026-09-01 12:07 ` [PATCH net-next 9/9] net: bridge: vlan: use br_vlan_get_state to get vlan state Nikolay Aleksandrov
2026-09-02 17:22 ` Nikolay Aleksandrov [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=239e8a53-fb02-4021-8f74-6c232e9c9b6f@blackwall.org \
    --to=razor@blackwall.org \
    --cc=bridge@lists.linux.dev \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=idosch@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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