multiple wireguard interface and kworker ressources

nicolas prochazka prochazka.nicolas at
Wed Jun 14 16:17:08 CEST 2017

thanks :)

2017-06-14 16:13 GMT+02:00 Jason A. Donenfeld <Jason at>:
> On Wed, Jun 14, 2017 at 4:05 PM, Jason A. Donenfeld <Jason at> wrote:
>> Will keep a kworker at 100% CPU, even after that command completes?
>> I'm unable to reproduce this here. Could you give me detailed
>> environmental information so that I can reproduce this precisely?
>> Something minimal and easily reproducable would be preferred.
> Okay, I have a working reproducer now, and I've isolated the issue to
> the xt_hashlimit garbage collector, an issue outside the WireGuard
> code base. I might look for a work around within WireGuard, however.
> I'll keep you posted.

More information about the WireGuard mailing list