Memleak with 0.0.20171221-5 on Debian stretch

[Baptiste Jonglez]

Hi Jason,

On 12-02-18, Jason A. Donenfeld wrote:
> 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?

It's the latter "day-in-day-out" option: the system has a single wireguard
interface, which is configured once at boot-time, and then used
extensively to forward traffic.  It tends to encrypt more than it
decrypts.

> 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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.zx2c4.com/pipermail/wireguard/attachments/20180212/e07d8ba7/attachment-0001.asc>