From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: Sven Eckelmann <sven@narfation.org>
Subject: [PATCH RFC batadv v4 2/8] batman-adv: tt: extract code handling a roam on add
Date: Thu, 06 Aug 2026 09:41:27 +0200 [thread overview]
Message-ID: <20260806-tt-fixes-v4-2-c2fc871fe807@narfation.org> (raw)
In-Reply-To: <20260806-tt-fixes-v4-0-c2fc871fe807@narfation.org>
The code for handling the roaming of clients is mostly self contained but
embedded in the already too large batadv_tt_local_add function. The
maintainability can be improved by keeping it in an separate function.
Signed-off-by: Sven Eckelmann <sven@narfation.org>
---
net/batman-adv/translation-table.c | 71 ++++++++++++++++++++++++--------------
1 file changed, 45 insertions(+), 26 deletions(-)
diff --git a/net/batman-adv/translation-table.c b/net/batman-adv/translation-table.c
index af40ff81..2a1d8963 100644
--- a/net/batman-adv/translation-table.c
+++ b/net/batman-adv/translation-table.c
@@ -667,6 +667,50 @@ static void batadv_tt_global_free(struct batadv_priv *bat_priv,
batadv_tt_global_entry_put(tt_global);
}
+/**
+ * batadv_tt_local_add_roam() - handle roamed clients during batadv_tt_local_add()
+ * @bat_priv: the bat priv with all the mesh interface information
+ * @tt_global: the global TT entry
+ * @roamed_back: whether @tt_global roamed back
+ */
+static void batadv_tt_local_add_roam(struct batadv_priv *bat_priv,
+ struct batadv_tt_global_entry *tt_global,
+ bool roamed_back)
+{
+ struct batadv_tt_orig_list_entry *orig_entry;
+ struct hlist_head *head;
+
+ if (!tt_global)
+ return;
+
+ /* Check whether it is a roaming, but don't do anything if the roaming
+ * process has already been handled
+ */
+ if (tt_global->common.flags & BATADV_TT_CLIENT_ROAM)
+ return;
+
+ /* These node are probably going to update their tt table */
+ head = &tt_global->orig_list;
+ rcu_read_lock();
+ hlist_for_each_entry_rcu(orig_entry, head, list) {
+ batadv_send_roam_adv(bat_priv, tt_global->common.addr,
+ tt_global->common.vid,
+ orig_entry->orig_node);
+ }
+ rcu_read_unlock();
+
+ if (roamed_back) {
+ batadv_tt_global_free(bat_priv, tt_global,
+ "Roaming canceled");
+ } else {
+ /* The global entry has to be marked as ROAMING and
+ * has to be kept for consistency purpose
+ */
+ tt_global->common.flags |= BATADV_TT_CLIENT_ROAM;
+ tt_global->roam_at = jiffies;
+ }
+}
+
/**
* batadv_tt_local_add() - add a new client to the local table or update an
* existing client
@@ -685,14 +729,12 @@ bool batadv_tt_local_add(struct net_device *mesh_iface, const u8 *addr,
{
struct batadv_priv *bat_priv = netdev_priv(mesh_iface);
struct batadv_tt_global_entry *tt_global = NULL;
- struct batadv_tt_orig_list_entry *orig_entry;
struct batadv_tt_local_entry *tt_local;
struct net *net = dev_net(mesh_iface);
struct net_device *in_dev = NULL;
struct batadv_meshif_vlan *vlan;
bool roamed_back = false;
bool iif_is_wifi = false;
- struct hlist_head *head;
int packet_size_max;
bool ret = false;
u8 remote_flags;
@@ -811,30 +853,7 @@ bool batadv_tt_local_add(struct net_device *mesh_iface, const u8 *addr,
batadv_tt_local_event(bat_priv, tt_local, BATADV_NO_FLAGS);
check_roaming:
- /* Check whether it is a roaming, but don't do anything if the roaming
- * process has already been handled
- */
- if (tt_global && !(tt_global->common.flags & BATADV_TT_CLIENT_ROAM)) {
- /* These node are probably going to update their tt table */
- head = &tt_global->orig_list;
- rcu_read_lock();
- hlist_for_each_entry_rcu(orig_entry, head, list) {
- batadv_send_roam_adv(bat_priv, tt_global->common.addr,
- tt_global->common.vid,
- orig_entry->orig_node);
- }
- rcu_read_unlock();
- if (roamed_back) {
- batadv_tt_global_free(bat_priv, tt_global,
- "Roaming canceled");
- } else {
- /* The global entry has to be marked as ROAMING and
- * has to be kept for consistency purpose
- */
- tt_global->common.flags |= BATADV_TT_CLIENT_ROAM;
- tt_global->roam_at = jiffies;
- }
- }
+ batadv_tt_local_add_roam(bat_priv, tt_global, roamed_back);
/* store the current remote flags before altering them. This helps
* understanding is flags are changing or not
--
2.47.3
next prev parent reply other threads:[~2026-08-06 7:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 7:41 [PATCH RFC batadv v4 0/8] batman-adv: tt: atomic sashiko fixes Sven Eckelmann
2026-08-06 7:41 ` [PATCH RFC batadv v4 1/8] batman-adv: tt: remove only the entry which was looked up from the hash Sven Eckelmann
2026-08-06 7:41 ` Sven Eckelmann [this message]
2026-08-06 7:41 ` [PATCH RFC batadv v4 3/8] batman-adv: tt: simplify NEW flag transition code Sven Eckelmann
2026-08-06 7:41 ` [PATCH RFC batadv v4 4/8] batman-adv: tt: drop unnecessary cleanup goto in helpers Sven Eckelmann
2026-08-06 7:41 ` [PATCH RFC batadv v4 5/8] batman-adv: tt: use protected flag modifications Sven Eckelmann
2026-08-06 7:41 ` [PATCH RFC batadv v4 6/8] batman-adv: tt: transition NEW local entries only under lock Sven Eckelmann
2026-08-06 7:41 ` [PATCH RFC batadv v4 7/8] batman-adv: tt: don't uncount never committed clients on pending purge Sven Eckelmann
2026-08-06 7:41 ` [PATCH RFC batadv v4 8/8] batman-adv: tt: decrement count for committed client on local_remove Sven Eckelmann
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=20260806-tt-fixes-v4-2-c2fc871fe807@narfation.org \
--to=sven@narfation.org \
--cc=b.a.t.m.a.n@lists.open-mesh.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