B.A.T.M.A.N Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [PATCH RFC batadv v4 7/7] batman-adv: iv: drop migration check for batadv_hard_iface
Date: Sun, 07 Jun 2026 14:28:08 +0200	[thread overview]
Message-ID: <2859324.mvXUDI8C0e@sven-desktop> (raw)
In-Reply-To: <20260607-drop-hardif-list-v4-7-ade2931db295@narfation.org>

[-- Attachment #1: Type: text/plain, Size: 1709 bytes --]

On Sunday, 7 June 2026 13:54:01 CEST Sven Eckelmann wrote:
> With the immutability guarantee of batadv_hard_iface->mesh_iface, the check
> for "changed" (or NULL) mesh_iface is no longer necessary because and
> batadv_hard_iface can no longer migrate from one batadv_mesh_iface to
> another one.
> 
> Signed-off-by: Sven Eckelmann <sven@narfation.org>
> ---
>  net/batman-adv/bat_iv_ogm.c | 5 -----
>  1 file changed, 5 deletions(-)
> 
> diff --git a/net/batman-adv/bat_iv_ogm.c b/net/batman-adv/bat_iv_ogm.c
> index d9e4d023..89803a8a 100644
> --- a/net/batman-adv/bat_iv_ogm.c
> +++ b/net/batman-adv/bat_iv_ogm.c
> @@ -407,11 +407,6 @@ static void batadv_iv_ogm_emit(struct batadv_forw_packet *forw_packet)
>  	if (WARN_ON(!forw_packet->if_outgoing))
>  		return;
>  
> -	if (forw_packet->if_outgoing->mesh_iface != mesh_iface) {
> -		pr_warn("%s: mesh interface switch for queued OGM\n", __func__);
> -		return;
> -	}
> -
>  	if (forw_packet->if_incoming->if_status != BATADV_IF_ACTIVE)
>  		return;
>  
> 
> 

This should be added with the next revision:

diff --git i/net/batman-adv/bat_iv_ogm.c w/net/batman-adv/bat_iv_ogm.c
index 89803a8a..43440ccd 100644
--- i/net/batman-adv/bat_iv_ogm.c
+++ w/net/batman-adv/bat_iv_ogm.c
@@ -395,15 +395,11 @@ static void batadv_iv_ogm_send_to_if(struct batadv_forw_packet *forw_packet,
 /* send a batman ogm packet */
 static void batadv_iv_ogm_emit(struct batadv_forw_packet *forw_packet)
 {
-	struct net_device *mesh_iface;
-
 	if (!forw_packet->if_incoming) {
 		pr_err("Error - can't forward packet: incoming iface not specified\n");
 		return;
 	}
 
-	mesh_iface = forw_packet->if_incoming->mesh_iface;
-
 	if (WARN_ON(!forw_packet->if_outgoing))
 		return;
 

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      reply	other threads:[~2026-06-07 12:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-07 11:53 [PATCH RFC batadv v4 0/7] batman-adv: drop global hard interface list Sven Eckelmann
2026-06-07 11:53 ` [PATCH RFC batadv v4 1/7] batman-adv: only create hardif while a netdev is part of a mesh Sven Eckelmann
2026-06-07 11:53 ` [PATCH RFC batadv v4 2/7] batman-adv: remove global hardif list Sven Eckelmann
2026-06-07 11:53 ` [PATCH RFC batadv v4 3/7] batman-adv: remove BATADV_IF_NOT_IN_USE hardif state Sven Eckelmann
2026-06-07 11:53 ` [PATCH RFC batadv v4 4/7] batman-adv: move hardif generation counter into batadv_priv Sven Eckelmann
2026-06-07 11:53 ` [PATCH RFC batadv v4 5/7] batman-adv: drop NULL check for immutable hardif->mesh_iface Sven Eckelmann
2026-06-07 11:54 ` [PATCH RFC batadv v4 6/7] Revert "batman-adv: v: stop OGMv2 on disabled interface" Sven Eckelmann
2026-06-07 11:54 ` [PATCH RFC batadv v4 7/7] batman-adv: iv: drop migration check for batadv_hard_iface Sven Eckelmann
2026-06-07 12:28   ` Sven Eckelmann [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=2859324.mvXUDI8C0e@sven-desktop \
    --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