Netdev List
 help / color / mirror / Atom feed
From: Nikolay Aleksandrov <razor@blackwall.org>
To: Eric Dumazet <edumazet@google.com>,
	"David S . Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: Simon Horman <horms@kernel.org>, Ido Schimmel <idosch@nvidia.com>,
	netdev@vger.kernel.org, eric.dumazet@gmail.com
Subject: Re: [PATCH v2 net-next 05/11] bridge: provide lockless access to p->path_cost
Date: Wed, 3 Jun 2026 10:44:05 +0300	[thread overview]
Message-ID: <320bf57b-ec91-4aca-bf57-de8d8d9cda30@blackwall.org> (raw)
In-Reply-To: <20260603062043.3911278-6-edumazet@google.com>

On 03/06/2026 09:20, Eric Dumazet wrote:
> Add READ_ONCE()/WRITE_ONCE() annotations around p->path_cost.
> 
> This is needed at least for sysfs show_path_cost(), BRCTL_GET_PORT_INFO
> and upcoming RTNL avoidance in "ip link" dumps (cf br_port_fill_attrs()).
> 
> Signed-off-by: Eric Dumazet <edumazet@google.com>
> ---
>   net/bridge/br_if.c       |  2 +-
>   net/bridge/br_ioctl.c    |  2 +-
>   net/bridge/br_netlink.c  |  2 +-
>   net/bridge/br_stp.c      | 17 +++++++++++------
>   net/bridge/br_stp_if.c   |  2 +-
>   net/bridge/br_sysfs_if.c |  2 +-
>   6 files changed, 16 insertions(+), 11 deletions(-)
> 

Acked-by: Nikolay Aleksandrov <razor@blackwall.org>


  reply	other threads:[~2026-06-03  7:44 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-03  6:20 [PATCH v2 net-next 00/11] bridge: prepare lockless br_port_fill_attrs() (I) Eric Dumazet
2026-06-03  6:20 ` [PATCH v2 net-next 01/11] bridge: add a READ_ONCE() in br_timer_value() Eric Dumazet
2026-06-03  7:42   ` Nikolay Aleksandrov
2026-06-03  6:20 ` [PATCH v2 net-next 02/11] bridge: add bridge_flags_bit enum Eric Dumazet
2026-06-03  7:42   ` Nikolay Aleksandrov
2026-06-03  6:20 ` [PATCH v2 net-next 03/11] bridge: use BR_PROMISC_BIT Eric Dumazet
2026-06-03  7:42   ` Nikolay Aleksandrov
2026-06-03  6:20 ` [PATCH v2 net-next 04/11] bridge: use BR_ADMIN_COST_BIT Eric Dumazet
2026-06-03  7:43   ` Nikolay Aleksandrov
2026-06-03  6:20 ` [PATCH v2 net-next 05/11] bridge: provide lockless access to p->path_cost Eric Dumazet
2026-06-03  7:44   ` Nikolay Aleksandrov [this message]
2026-06-03  6:20 ` [PATCH v2 net-next 06/11] bridge: provide lockless access to p->designated_cost Eric Dumazet
2026-06-03  7:46   ` Nikolay Aleksandrov
2026-06-03  6:20 ` [PATCH v2 net-next 07/11] bridge: provide lockless access to p->designated_port Eric Dumazet
2026-06-03  7:47   ` Nikolay Aleksandrov
2026-06-03  6:20 ` [PATCH v2 net-next 08/11] bridge: provide lockless access to p->priority Eric Dumazet
2026-06-03  7:49   ` Nikolay Aleksandrov
2026-06-03  6:20 ` [PATCH v2 net-next 09/11] bridge: provide lockless access to p->port_id Eric Dumazet
2026-06-03  7:50   ` Nikolay Aleksandrov
2026-06-03  6:20 ` [PATCH v2 net-next 10/11] bridge: provide lockless access to p->config_pending Eric Dumazet
2026-06-03  7:51   ` Nikolay Aleksandrov
2026-06-03  6:20 ` [PATCH v2 net-next 11/11] bridge: read p->flags once in br_port_fill_attrs() Eric Dumazet
2026-06-03  7:52   ` Nikolay Aleksandrov

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=320bf57b-ec91-4aca-bf57-de8d8d9cda30@blackwall.org \
    --to=razor@blackwall.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.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