From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: samuel@sholland.org Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id ed690268 for ; Wed, 2 Nov 2016 06:11:03 +0000 (UTC) To: "Jason A. Donenfeld" References: <1e33f311-9d18-6822-cf9e-e3d93da0af21@sholland.org> From: Samuel Holland Message-ID: Date: Wed, 2 Nov 2016 01:12:07 -0500 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed 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: , Hello, On 11/02/2016 12:39 AM, Jason A. Donenfeld wrote: > I believe it's fixed now with the current commits in master. I'll tag > a new snapshot if the problems go away. Great. I don't think it caused any noticeable side-effects; I just saw the warning. > My question still stands, though -- is this issue repeatable, or was > it a one-off event? It was just something I happened to notice in dmesg. I don't know if it has happened before because I only recently started logging kernel messages to disk on that machine. I do note that the warning is WARN_ON_ONCE, so it will only show up in logs once per boot. > Thanks, > Jason Thanks, Samuel