From: Markus Grundmann <markus@activezone.de>
To: wireguard@lists.zx2c4.com
Subject: DMKS failed after Kernel Upgrade to 4.4.0-161-generic on Ubuntu 16.04 LTS
Date: Fri, 6 Sep 2019 09:32:45 +0200 [thread overview]
Message-ID: <a8a4d088-d5fd-5e3b-23ab-72e2c7932ff3@activezone.de> (raw)
Question: If the patch needed?
Don't touch a running system :-|
-Markus
[..]
Selecting previously unselected package wireguard-dkms.
(Reading database ... 346239 files and directories currently installed.)
Preparing to unpack .../wireguard-dkms_0.0.20190702-wg1~xenial_all.deb ...
Unpacking wireguard-dkms (0.0.20190702-wg1~xenial) ...
Selecting previously unselected package wireguard-tools.
Preparing to unpack
.../wireguard-tools_0.0.20190702-wg1~xenial_amd64.deb ...
Unpacking wireguard-tools (0.0.20190702-wg1~xenial) ...
Selecting previously unselected package wireguard.
Preparing to unpack .../wireguard_0.0.20190702-wg1~xenial_all.deb ...
Unpacking wireguard (0.0.20190702-wg1~xenial) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up wireguard-dkms (0.0.20190702-wg1~xenial) ...
Loading new wireguard-0.0.20190702 DKMS files...
First Installation: checking all kernels...
Building only for 4.4.0-161-generic
Building initial module for 4.4.0-161-generic
ERROR: Cannot create report: [Errno 17] File exists:
'/var/crash/wireguard-dkms.0.crash'
Error! Bad return status for module build on kernel: 4.4.0-161-generic
(x86_64)
Consult /var/lib/dkms/wireguard/0.0.20190702/build/make.log for more
information.
Setting up wireguard-tools (0.0.20190702-wg1~xenial) ...
Setting up wireguard (0.0.20190702-wg1~xenial) ...
=== Crash Report ===
ProblemType: Package
DKMSBuildLog:
DKMS make.log for wireguard-0.0.20190702 for kernel 4.4.0-161-generic
(x86_64)
Fr 6. Sep 09:02:18 CEST 2019
make: Entering directory '/usr/src/linux-headers-4.4.0-161-generic'
LD /var/lib/dkms/wireguard/0.0.20190702/build/built-in.o
CC [M] /var/lib/dkms/wireguard/0.0.20190702/build/main.o
CC [M] /var/lib/dkms/wireguard/0.0.20190702/build/noise.o
CC [M] /var/lib/dkms/wireguard/0.0.20190702/build/device.o
CC [M] /var/lib/dkms/wireguard/0.0.20190702/build/peer.o
CC [M] /var/lib/dkms/wireguard/0.0.20190702/build/timers.o
CC [M] /var/lib/dkms/wireguard/0.0.20190702/build/queueing.o
CC [M] /var/lib/dkms/wireguard/0.0.20190702/build/send.o
CC [M] /var/lib/dkms/wireguard/0.0.20190702/build/receive.o
CC [M] /var/lib/dkms/wireguard/0.0.20190702/build/socket.o
CC [M] /var/lib/dkms/wireguard/0.0.20190702/build/peerlookup.o
CC [M] /var/lib/dkms/wireguard/0.0.20190702/build/allowedips.o
/var/lib/dkms/wireguard/0.0.20190702/build/allowedips.c: In function
‘root_remove_peer_lists’:
/var/lib/dkms/wireguard/0.0.20190702/build/allowedips.c:72:1: warning:
the frame size of 1048 bytes is larger than 1024 bytes
[-Wframe-larger-than=]
}
^
/var/lib/dkms/wireguard/0.0.20190702/build/allowedips.c: In function
‘root_free_rcu’:
/var/lib/dkms/wireguard/0.0.20190702/build/allowedips.c:59:1: warning:
the frame size of 1048 bytes is larger than 1024 bytes
[-Wframe-larger-than=]
}
^
/var/lib/dkms/wireguard/0.0.20190702/build/allowedips.c: In function
‘walk_remove_by_peer.isra.3’:
/var/lib/dkms/wireguard/0.0.20190702/build/allowedips.c:126:1: warning:
the frame size of 1032 bytes is larger than 1024 bytes
[-Wframe-larger-than=]
}
^
CC [M] /var/lib/dkms/wireguard/0.0.20190702/build/ratelimiter.o
/var/lib/dkms/wireguard/0.0.20190702/build/ratelimiter.c:25:8: error:
unknown type name ‘hsiphash_key_t’
static hsiphash_key_t key;
^
/var/lib/dkms/wireguard/0.0.20190702/build/ratelimiter.c: In function
‘wg_ratelimiter_allow’:
/var/lib/dkms/wireguard/0.0.20190702/build/ratelimiter.c:109:22: error:
implicit declaration of function ‘hsiphash_2u32’
[-Werror=implicit-function-declaration]
bucket = &table_v4[hsiphash_2u32(net_word, ip, &key) &
^
/var/lib/dkms/wireguard/0.0.20190702/build/ratelimiter.c:116:22: error:
implicit declaration of function ‘hsiphash_3u32’
[-Werror=implicit-function-declaration]
bucket = &table_v6[hsiphash_3u32(net_word, ip >> 32, ip, &key) &
^
cc1: some warnings being treated as errors
scripts/Makefile.build:285: recipe for target
'/var/lib/dkms/wireguard/0.0.20190702/build/ratelimiter.o' failed
make[1]: *** [/var/lib/dkms/wireguard/0.0.20190702/build/ratelimiter.o]
Error 1
Makefile:1454: recipe for target
'_module_/var/lib/dkms/wireguard/0.0.20190702/build' failed
make: *** [_module_/var/lib/dkms/wireguard/0.0.20190702/build] Error 2
make: Leaving directory '/usr/src/linux-headers-4.4.0-161-generic'
DKMSKernelVersion: 4.4.0-161-generic
Date: Fri Sep 6 09:02:28 2019
DuplicateSignature:
dkms:wireguard-dkms:0.0.20190702-wg1~xenial:/var/lib/dkms/wireguard/0.0.20190702/build/ratelimiter.c:25:8:
error: unknown type name ‘hsiphash_key_t’
Package: wireguard-dkms 0.0.20190702-wg1~xenial
PackageVersion: 0.0.20190702-wg1~xenial
SourcePackage: wireguard
Title: wireguard-dkms 0.0.20190702-wg1~xenial: wireguard kernel module
failed to build
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next reply other threads:[~2019-09-06 7:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 7:32 Markus Grundmann [this message]
2019-09-06 14:06 ` Jason A. Donenfeld
2019-09-06 15:00 ` Markus Grundmann
2019-09-06 18:18 ` Jason A. Donenfeld
2019-09-06 19:51 ` Egbert Verhage
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=a8a4d088-d5fd-5e3b-23ab-72e2c7932ff3@activezone.de \
--to=markus@activezone.de \
--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).