All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: Matthias Schiffer <mschiffer@universe-factory.net>
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [PATCH batadv 2/5] batman-adv: only create hardif while a netdev is part of a mesh
Date: Sun, 10 May 2026 15:59:34 +0200	[thread overview]
Message-ID: <12908485.O9o76ZdvQC@sven-desktop> (raw)
In-Reply-To: <6005840.1IzOArtZ34@sven-desktop>

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

On Saturday, 31 May 2025 11:52:12 CEST Sven Eckelmann wrote:
> On Monday, 19 May 2025 22:46:29 CEST Matthias Schiffer wrote:
> > -int batadv_hardif_enable_interface(struct batadv_hard_iface *hard_iface,
> > +int batadv_hardif_enable_interface(struct net_device *net_dev,
> >                                    struct net_device *mesh_iface)
> >  {
> [....]
> > +       hard_iface->wifi_flags = batadv_wifi_flags_evaluate(net_dev);
> 
> Moving this here should break the WIFI TT flag in scenarios like this:
> 
>                    ┌──────┐             
>        ┌───────────┼br-lan├──────┐      
>        │           └──────┘      │      
>        │                         │      
>        │                         │      
>      ┌─▼─┐                    ┌──▼─┐    
>      │ap0│                    │bat0│    
>      └───┘                    └──┬─┘    
>                                  │      
>                                  │      
>                               ┌──▼──┐   
>                               │mesh0│   
>                               └─────┘   
> 
> 
> ap0 is not the lower interface of any batadv mesh interface but TT ap 
> isolation is depending on the information stored for this hardif. See:

I have now posted 
https://patchwork.open-mesh.org/project/b.a.t.m.a.n./patch/20260510-hardif-wifi-cache-v1-1-6dce5ee6b0f9@narfation.org/
to separate the wifi flags from the code (around batadv_hardif) which you 
try to modify.

Regards,
	Sven

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

  reply	other threads:[~2026-05-10 14:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-19 20:46 [PATCH batadv 1/5] batman-adv: store hard_iface as iflink private data Matthias Schiffer
2025-05-19 20:46 ` [PATCH batadv 2/5] batman-adv: only create hardif while a netdev is part of a mesh Matthias Schiffer
2025-05-31  9:16   ` Sven Eckelmann
2025-05-31  9:21     ` Sven Eckelmann
2025-05-31  9:52   ` Sven Eckelmann
2026-05-10 13:59     ` Sven Eckelmann [this message]
2025-05-19 20:46 ` [PATCH batadv 3/5] batman-adv: remove BATADV_IF_NOT_IN_USE hardif state Matthias Schiffer
2025-05-31  9:18   ` Sven Eckelmann
2025-05-19 20:46 ` [PATCH batadv 4/5] batman-adv: remove global hardif list Matthias Schiffer
2025-05-31  9:56   ` Sven Eckelmann
2025-06-01  9:26     ` Matthias Schiffer
2025-06-01 13:10       ` Sven Eckelmann
2025-06-01 13:36         ` Sven Eckelmann
2026-05-10  7:30   ` Sven Eckelmann
2025-05-19 20:46 ` [PATCH batadv 5/5] batman-adv: move hardif generation counter into batadv_priv Matthias Schiffer
2025-05-31  9:59   ` Sven Eckelmann
2025-05-31  8:31 ` [PATCH batadv 1/5] batman-adv: store hard_iface as iflink private data 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=12908485.O9o76ZdvQC@sven-desktop \
    --to=sven@narfation.org \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=mschiffer@universe-factory.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.