Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Pascal Ernster <pascal.ernster+wireguard@rub.de>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Ubuntu kernel >= 5.3.0-52.46 breaks DKMS build for wireguard-linux-compat >= 1.0.20200429, patch included
Date: Tue, 5 May 2020 05:52:24 +0200	[thread overview]
Message-ID: <20328df0-e2dd-1653-9fc1-1fb06cbc054f@rub.de> (raw)
In-Reply-To: <CAHmME9qDMiNh90_zA9KsFX-OaHNUHnw5=e65jH3PdXg1n7nyFw@mail.gmail.com>

Hi Jason,


[2020-05-05 03:37] Jason A. Donenfeld:
> Can you confirm to me whether or not this patch fixes the issue on
> both 19.10 and 18.04-hwe?
> 
> https://git.zx2c4.com/wireguard-linux-compat/commit/?id=1325bedf8ee3d69ed58460b7a8fee96d949f67da

I don't have a 19.10 machine to test on, but at least on an 18.04
machine with the 5.3.0-52.46 kernel, it works as intended.

However, building the module for the previous 5.3.0-51.44 kernel fails
now, and it doesn't fail when I use my original patch.

Note that as of now, 5.3.0-51.44 is still the latest "official" HWE
kernel for 18.04, and 5.3.0-52.46 is only available from Ubuntu's
"bionic-proposed" repo.


Regards
Pascal

-- 
Forschung und wissenschaftliche Informationsversorgung
IT.SERVICES
Ruhr-Universität Bochum | 44780 Bochum
Fon: +49 234 32-29169
Fax: +49 234 32-07835

  reply	other threads:[~2020-05-05  3:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-03 20:33 Pascal Ernster
2020-05-05  1:37 ` Jason A. Donenfeld
2020-05-05  3:52   ` Pascal Ernster [this message]
2020-05-05  4:03     ` Jason A. Donenfeld
2020-05-05  4:27       ` Pascal Ernster
2020-05-06 16:22       ` Simon Deziel
2020-05-07  0:29         ` Jason A. Donenfeld
2020-05-20 15:04         ` Vasili Pupkin

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=20328df0-e2dd-1653-9fc1-1fb06cbc054f@rub.de \
    --to=pascal.ernster+wireguard@rub.de \
    --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).