On Fri, 04 Aug 2023 11:39:36 +0200, Remi Pommarel wrote:
> When a client roamed back to a node before it got time to destroy the
> pending local entry (i.e. within the same originator interval) the old
> global one is directly removed from hash table and left as such.
>
> But because this entry had an extra reference taken at lookup (i.e using
> batadv_tt_global_hash_find) there is no way its memory will be reclaimed
> at any time causing the following memory leak:
>
> [...]
Applied, thanks!
[1/1] batman-adv: Fix TT global entry leak when client roamed back
commit: d25ddb7e788d34cf27ff1738d11a87cb4b67d446
Kind regards,
SvenAttachment:
signature.asc
Description: This is a digitally signed message part.
