From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Jason@zx2c4.com Received: from frisell.zx2c4.com (frisell.zx2c4.com [192.95.5.64]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id abaf81cf for ; Wed, 2 Nov 2016 05:38:54 +0000 (UTC) Received: by frisell.zx2c4.com (ZX2C4 Mail Server) with ESMTP id e1ae3666 for ; Wed, 2 Nov 2016 05:38:53 +0000 (UTC) Received: by frisell.zx2c4.com (ZX2C4 Mail Server) with ESMTPSA id 992cefb4 (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128:NO) for ; Wed, 2 Nov 2016 05:38:53 +0000 (UTC) Received: by mail-lf0-f43.google.com with SMTP id b81so3647471lfe.1 for ; Tue, 01 Nov 2016 22:39:58 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <1e33f311-9d18-6822-cf9e-e3d93da0af21@sholland.org> From: "Jason A. Donenfeld" Date: Wed, 2 Nov 2016 06:39:56 +0100 Message-ID: To: Samuel Holland Content-Type: text/plain; charset=UTF-8 Cc: WireGuard mailing list Subject: Re: [WireGuard] Kernel warning from WireGuard module List-Id: Development discussion of WireGuard List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hi Samuel, I believe it's fixed now with the current commits in master. I'll tag a new snapshot if the problems go away. My question still stands, though -- is this issue repeatable, or was it a one-off event? Thanks, Jason