[PATCH batadv v3 0/2] batman-adv: BLA fixes for sashiko reports

Sven Eckelmann <[email protected]>
Newsgroups org.open-mesh.lists.batman
Message-ID <[email protected]>
There were new sashiko reports for bridge-loop-avoidance

* https://sashiko.dev/#/patchset/[email protected]?part=7
* https://sashiko.dev/#/patchset/[email protected]?part=1
* https://sashiko.dev/#/patchset/[email protected]?part=1
* https://sashiko.dev/#/patchset/20260513-bla-cancel-work-v2-0-9c17d82d7e2d%40narfation.org

These can be easily^W tackled. But they must be done at the same time
because they are modifying similar places.

Signed-off-by: Sven Eckelmann <[email protected]>
---
Changes in v3:
- get rid of the idea of being able to protect num_requests with only a
  boolean "request_sent", instead introduce a third state "stopped" to
  prevent num_requests++/-- after batadv_bla_purge_backbone_gw() ran
- ignore Simons Reviewed-by bla.num_requests patch because the original
  patch turned out to not work out in this version
- convert also wait_periods to a simple u8 and prevent it from underflowing
- Link to v2: https://patch.msgid.link/[email protected]

Changes in v2:
- add patch from (to avoid conflicts)
  https://patch.msgid.link/[email protected]
- modify bla.num_requests patch to use lock over both request_sent and
  num_requests
- Link to v1: https://patch.msgid.link/[email protected]

---
Sven Eckelmann (2):
      batman-adv: bla: fix report_work leak on backbone_gw purge
      batman-adv: bla: avoid double decrement of bla.num_requests

 net/batman-adv/bridge_loop_avoidance.c | 103 ++++++++++++++++++++++-----------
 net/batman-adv/mesh-interface.c        |   1 +
 net/batman-adv/types.h                 |  39 ++++++++++---
 3 files changed, 101 insertions(+), 42 deletions(-)
---
base-commit: 57c6af492c1948145db835bb3ea2980472558298
change-id: 20260510-bla-cancel-work-8dc6f3c2cb14

Best regards,
--  
Sven Eckelmann <[email protected]>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.