From: Gregory ORIOL <fortin81@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: Problems with Ubuntu 16.04 kernels and wireguard 1.0.20200611
Date: Sun, 14 Jun 2020 15:54:12 +0200 [thread overview]
Message-ID: <56455548-76ff-1f8e-9aff-e0bd45d8daa3@gmail.com> (raw)
Hi,
Since commit e24c9a9265af40781fa27b5de11dd5b78925c5be to
wireguard-linux-compat with a fix for some Ubuntu versions, we are
experiencing a problem with some older, but still LTS, versions of
Ubuntu 16.04: older kernels 4.4.0-148, 4.4.0-166 fail to build with
wireguard 1.0.20200611
So, any system running an (or still having an installed) "older" kernel
and doing an apt upgrade to install wireguard 1.0.20200611 would fail
during the wireguard dkms step, while trying to build wireguard for all
the kernels available.
The problem gets more problematic when a newer kernel 4.4.0-184 gets
installed with the same apt upgrade: then, trying to downgrade wireguard
also fails; none of the 1.0.20200611 or 1.0.20200520 versions work
anymore with this combination of old/new kernels...
To recap :
# wireguard 1.0.20200520
- ok with kernels 4.4.0-148, 4.4.0-166
- fails with kernel 4.4.0-184
# wireguard 1.0.20200611
- fails with kernels 4.4.0-148, 4.4.0-166
- ok with kernel 4.4.0-184
(nb: we see it now with -184 but it could have started with an earlier
version)
We could partially fix this by manually getting each deb/src and doing
dkms install:
dkms install wireguard/1.0.20200520 -k 4.4.0-148-generic
dkms install wireguard/1.0.20200611 -k 4.4.0-184-generic
...
But apt upgrade is still broken.
While we could boot onto the newer kernel and remove the older ones to
get rid of the problem, this situation would prevent from having a
"previous working" kernel on the system, which is not very safe.
Could there be a fix for this made to wireguard-linux-compat for those
versions?
Best regards,
Greg
next reply other threads:[~2020-06-17 7:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-14 13:54 Gregory ORIOL [this message]
2020-06-17 8:13 ` Jason A. Donenfeld
2020-06-17 11:03 ` Gregory ORIOL
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=56455548-76ff-1f8e-9aff-e0bd45d8daa3@gmail.com \
--to=fortin81@gmail.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).