netdev - Required guidance to debug ipsec memory leak

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 18 Nov 2019 06:35:24 +0000
From:   Vakul Garg <vakul.garg@....com>
To:     "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Required guidance to debug ipsec memory leak

Hi

I need help to debug a suspected memory leak problem while running kernel ipsec with rekeying enabled.
I am using strongswan for tunnel creation/maintainence and using kernel 5.4 (with e1000 ethernet adapters) on cortex-a72 based quadcore cpu.

My setup uses hub-and-spoke model (1 hub and 2-spokes).
In all there are 4 tunnels.

When traffic is running, the kernel shows that 'used' memory (in ''free'' command output) gets incremented steadily.
The system keeps loosing memory and eventually after several hours, OOM killer gets invoked.

The memory usage does not increase if traffic is not run (and simply rekeying is happening).
The memory depletes faster if rekey time is decreased or if number of tunnels in increased.

'Kmemleak' does not show up anything.

I checked that number of states (i.e. net->xfrm.state_num) does not increase much and states are getting freed as expected.

Kindly guide me about what else to check.

Regards

Vakul