Memleak with 0.0.20171221-5 on Debian stretch
Jason A. Donenfeld
Jason at zx2c4.com
Mon Feb 12 01:23:19 CET 2018
Thanks for the detailed report. Graphs like that are quite helpful.
I'm just back from a long weekend, so sorry for not having a chance to
look at this sooner.
I'm first curious about the basic "control group" issue Daniel
mentioned -- it's probably important to isolate if it's the new kernel
or the new module, or some complex interaction of the two.
Secondly, I'm wondering if you tend to do, "anything strange". For
example -- are you setting up and taking down the device often in an
automated way? Or reconfiguring the interface (via wg(8), for example)
often in an automated way? Or is the sustained day-in-day-out workload
that leads to this graph simply forwarding and encrypting/decrypting
packets as usual? If it's the latter, does this device tend to encrypt
or decrypt more, or both equally? In either case, I'm not sure too
much has changed between those version spans you gave, with regards to
the general packet encryption/decryption path, so I suspect this bug
will take some hunting to track down.
Thanks again for the report. Let me know about the kernel version situation.
More information about the WireGuard