From: Eric Dumazet <edumazet@google.com>
To: "David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>
Cc: Simon Horman <horms@kernel.org>,
Kuniyuki Iwashima <kuniyu@google.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
netdev@vger.kernel.org, eric.dumazet@gmail.com,
Eric Dumazet <edumazet@google.com>
Subject: [PATCH net-next 0/2] hsr: lockless hsr_fill_info()
Date: Wed, 16 Sep 2026 13:28:20 +0000 [thread overview]
Message-ID: <20260916132822.1791040-1-edumazet@google.com> (raw)
hsr_fill_info() currently relies on RTNL being held, because
hsr_port_get_hsr() walks hsr->ports with hsr_for_each_port_rtnl().
- Patch 1 annotates the data-race around hsr->sequence_nr, which
is incremented from the transmit paths under hsr->seqnr_lock but
read without it.
- Patch 2 converts hsr_fill_info() to RCU, using a local RCU
variant of hsr_port_get_hsr().
hsr->ports is already an RCU protected list: ports are added with
list_add_tail_rcu(), removed with list_del_rcu() and freed with
kfree_rcu(), and the data path already iterates over it with
hsr_for_each_port().
This is part of a larger effort to remove the RTNL dependency from
rtnl_link_ops->fill_info().
Eric Dumazet (2):
hsr: annotate data-race around hsr->sequence_nr
hsr: no longer rely on RTNL in hsr_fill_info()
net/hsr/hsr_device.c | 2 +-
net/hsr/hsr_forward.c | 2 +-
net/hsr/hsr_netlink.c | 35 ++++++++++++++++++++++++++---------
3 files changed, 28 insertions(+), 11 deletions(-)
--
2.55.0.1032.g73a4cd73de-goog
next reply other threads:[~2026-09-16 13:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 13:28 Eric Dumazet [this message]
2026-09-16 13:28 ` [PATCH net-next 1/2] hsr: annotate data-race around hsr->sequence_nr Eric Dumazet
2026-09-16 13:28 ` [PATCH net-next 2/2] hsr: no longer rely on RTNL in hsr_fill_info() Eric Dumazet
2026-09-19 0:10 ` [PATCH net-next 0/2] hsr: lockless hsr_fill_info() patchwork-bot+netdevbpf
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=20260916132822.1791040-1-edumazet@google.com \
--to=edumazet@google.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--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