Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Henry Snow <henry.snow@nielsen.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: "wireguard@lists.zx2c4.com" <wireguard@lists.zx2c4.com>
Subject: Re: wireguard-dkms and CentOS 7.5
Date: Thu, 10 May 2018 17:24:29 +0000	[thread overview]
Message-ID: <CAFuSFDFziCyiL=J_aom9YTWCM6gpGmY1cC56TroxJJvFcC3GKQ@mail.gmail.com> (raw)
In-Reply-To: <CAFuSFDEf9gUMW5nOcStnFM22dvAa_mAtMAVnk92m-dRY2xFa5w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1830 bytes --]

Well, I might have spoken too soon. As soon as a connection was established
to another wireguard peer (v. 0.0.20180118), the CentOS 7.5 server kernel
panic'd.

Message from syslogd@tun001 at May 10 12:53:12 ...
 kernel:Kernel panic - not syncing: Fatal exception in interrupt

Seeing something along the lines of this in the console output on boot:
[   29.418257] wireguard: loading out-of-tree module taints kernel.
[   29.454659] wireguard: WireGuard 0.0.20180420 loaded. See
www.wireguard.com for information.
[   29.464057] wireguard: Copyright (C) 2015-2018 Jason A. Donenfeld <
Jason@zx2c4.com>. All Rights R.
[   29.598028] ------------[ cut here ]------------
[   29.604356] kernel BUG at mm/slub.c:3601!
[   29.609122] invalid opcode: 0000 [#1] SMP
[   29.614013] Modules linked in: veth vxlan wireguard(OE) bridge stp llc
ip_vs ip6_udp_tunnel udp_tunnel bonding ip


On Thu, May 10, 2018 at 12:31 PM Henry Snow <henry.snow@nielsen.com> wrote:

> Perfect, that patch worked for me. Thank you for the quick fix!
>
>
> On Thu, May 10, 2018 at 12:14 PM Jason A. Donenfeld <Jason@zx2c4.com>
> wrote:
>
>> Hi again,
>>
>> I've fixed that here:
>>
>> https://git.zx2c4.com/WireGuard/patch/?id=94f25e47b23ddeba26120de4ee3c098438fc2251
>>
>> This will be part of the next snapshot. In the meantime, you can apply
>> that manually to the src directory, and perhaps Joe (CCd) can add it
>> to the rpm.
>>
>> Jason
>>
> --
> Henry Snow | Director, Site Reliability Engineering
> eXelate, a Nielsen company <http://exelate.com/>
> E: henry.snow@nielsen.com | M: 347.366.2700 <(347)%20366-2700>
> 675 6th Ave, 3rd Floor, New York, NY 10010
>
-- 
Henry Snow | Director, Site Reliability Engineering
eXelate, a Nielsen company <http://exelate.com/>
E: henry.snow@nielsen.com | M: 347.366.2700
675 6th Ave, 3rd Floor, New York, NY 10010

[-- Attachment #2: Type: text/html, Size: 4299 bytes --]

  reply	other threads:[~2018-05-10 17:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-10 13:59 Henry Snow
2018-05-10 15:34 ` Jason A. Donenfeld
2018-05-10 16:14   ` Jason A. Donenfeld
2018-05-10 16:31     ` Henry Snow
2018-05-10 17:24       ` Henry Snow [this message]
2018-05-10 17:25         ` Jason A. Donenfeld
2018-05-10 17:35           ` Henry Snow
2018-05-10 17:36             ` Jason A. Donenfeld
2018-05-10 17:49               ` Jason A. Donenfeld
2018-05-10 18:26                 ` Germano Massullo
2018-05-10 20:25                 ` Jason A. Donenfeld
2018-05-10 21:41                   ` Henry Snow
2018-05-10 21:47                     ` Jason A. Donenfeld
2018-05-11 16:07     ` Joe Doss
2018-05-11 16:15       ` Henry Snow
2018-05-13 16:56         ` Jason A. Donenfeld
  -- strict thread matches above, loose matches on Subject: below --
2018-05-10 13:50 Henry Snow

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAFuSFDFziCyiL=J_aom9YTWCM6gpGmY1cC56TroxJJvFcC3GKQ@mail.gmail.com' \
    --to=henry.snow@nielsen.com \
    --cc=Jason@zx2c4.com \
    --cc=wireguard@lists.zx2c4.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).