Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Egbert Verhage <egbert@eggiecode.org>,
	WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [WireGuard] Seeking Ubuntu PPA Maintainer
Date: Wed, 16 Nov 2016 01:12:05 +0100	[thread overview]
Message-ID: <CAHmME9p6mTNPuRgwqdzEx=emjtvh-R3R5HdSOB=E68_tQxdP5Q@mail.gmail.com> (raw)
In-Reply-To: <454ad249-3313-9423-c2d4-7602d56849fc@eggiecode.org>

Hey Egbert,

Great to see! How much does this deviate from debian's? As far as I
can tell, you should be able to keep things basically the same.


> Testing it constantly on 4 of my servers and works it great!
Happy to hear that.

> Even added a patch for ifupdown to setup WireGuard in
> /etc/network/interfaces
Cool!


> The only downside is that I disabled AVX2 cpu extention in the code,
> because of kernel panics on VPS's by a hosting company
> (https://eggiecode.org/wg-kernel-panic.png).

This isn't okay. Downstream packages really shouldn't be applying
patches like that. If you revert that, I can list this as the primary
PPA for WireGuard. With that said, let's actually try to fix this
issue for good...

AVX2 is advertised through CPUID. Is it possible that your VPS passes
through the CPUID from the host while not supporting all instructions?
Or perhaps, rather, fakes a CPUID that isn't the host's, while only
supporting instructions of the host? Very mysterious. What hosting
company is this? Is there a chance I can poke around at this setup? Do
you know if it's KVM or Xen or VMWare or something else?

If it turns out that your VPS host just does something horrible, I'll
look for a way to globally disable kernel usage of AVX2, without
having to patch WireGuard like that. If it's particular to the host,
perhaps we can come up with either a particular kernel module to do
the disabling, or some ungodly hack to /dev/kmem... Are you compiling
your own kernel for this system, or just using stock Ubuntu kernel?

I'm pretty sure, by the way, that we're using the right detection
function within WireGuard, seeing as every other place in the tree
uses the same thing: https://paste.kde.org/pdljfawf7/79eh62 .

Thanks a bunch for helping out.

Jason

  parent reply	other threads:[~2016-11-16  0:09 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-15 20:44 Jason A. Donenfeld
2016-11-15 23:41 ` Egbert Verhage
     [not found] ` <454ad249-3313-9423-c2d4-7602d56849fc@eggiecode.org>
2016-11-16  0:12   ` Jason A. Donenfeld [this message]
2016-11-16  0:34     ` Egbert Verhage
2016-11-16  1:31       ` Jason A. Donenfeld
2016-11-16  6:20         ` Dan Luedtke
2016-11-16 11:18           ` Egbert Verhage
2016-11-16 11:34             ` Dan Lüdtke
2016-11-16 14:04               ` Jason A. Donenfeld
2016-11-16 10:03         ` Egbert Verhage
2016-11-16 14:09           ` Jason A. Donenfeld
2016-11-16 14:22             ` Egbert Verhage
2016-11-16 14:25               ` Jason A. Donenfeld
2016-11-16  6:45       ` Daniel Kahn Gillmor
2016-11-16 11:10         ` Egbert Verhage
2016-11-16 14:24           ` Jason A. Donenfeld
2016-11-16 22:17             ` Daniel Kahn Gillmor
2016-11-16 22:52               ` Jason A. Donenfeld
2016-11-16 14:11 ` Jason A. Donenfeld
2016-11-16 14:37 Anonymous Anonymous
2016-11-16 15:00 ` Jason A. Donenfeld
2016-11-16 15:08   ` Egbert Verhage
2016-11-16 14:47 Anonymous Anonymous

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='CAHmME9p6mTNPuRgwqdzEx=emjtvh-R3R5HdSOB=E68_tQxdP5Q@mail.gmail.com' \
    --to=jason@zx2c4.com \
    --cc=egbert@eggiecode.org \
    --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).