8 Jun
2023
8 Jun
'23
4:57 p.m.
On Thursday, 8 June 2023 11:27:31 CEST Paolo Abeni wrote: [...]
We're still not preventing the timer / work from getting scheduled and staying alive after the netdev has been freed, right?
I *think* this specific use case does not expose such problem, as the delayed work is (AFAICS) scheduled only at device creation time and by the work itself, it should never be re-scheduled after cancel_delayed_work_sync()
Correct.
* batadv_dat_start_timer is the only thing scheduling it * batadv_dat_start_timer is called by:
- batadv_dat_purge (the worker rearming itself) - batadv_dat_init (when the interface is created)
Kind regards, Sven