From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "WireGuard mailing list" <wireguard@lists.zx2c4.com>
Subject: [ANNOUNCE] wireguard-linux-compat v1.0.20210606 released
Date: Sun, 06 Jun 2021 11:36:53 +0200 [thread overview]
Message-ID: <1649a9a43f0f2206@lists.zx2c4.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hello,
A new version, v1.0.20210606, of the backported WireGuard kernel module for
3.10 <= Linux <= 5.5.y has been tagged in the git repository.
== Changes ==
* netns: make sure rp_filter is disabled on vethc
* kbuild: do not use -O3
* global: use synchronize_net rather than synchronize_rcu
* peer: allocate in kmem_cache
* allowedips: initialize list head in selftest
* allowedips: remove nodes in O(1)
* allowedips: allocate nodes in kmem_cache
* allowedips: free empty intermediate nodes when removing single node
* allowedips: add missing __rcu annotation to satisfy sparse
* qemu: increase default dmesg log size
These are from the 5.13 pull request:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6fd815bb1ecc5d3cd99a31e0393fba0be517ed04
* qemu: add disgusting hacks for RHEL 8
Red Hat's latest kernel no longer compiles correctly, so we have to add all
sorts of hacks to fix it. I sent them some patches 6 months ago but they never
picked them up.
This release contains commits from: Jason A. Donenfeld.
As always, the source is available at https://git.zx2c4.com/wireguard-linux-compat/
and information about the project is available at https://www.wireguard.com/ .
This version is available in compressed tarball form here:
https://git.zx2c4.com/wireguard-linux-compat/snapshot/wireguard-linux-compat-1.0.20210606.tar.xz
SHA2-256: 3f5d990006e6eabfd692d925ec314fff2c5ee7dcdb869a6510d579acfdd84ec0
A PGP signature of that file decompressed is available here:
https://git.zx2c4.com/wireguard-linux-compat/snapshot/wireguard-linux-compat-1.0.20210606.tar.asc
Signing key: AB9942E6D4A4CFC3412620A749FC7012A5DE03AE
Remember to unxz the tarball before verifying the signature.
If you're a package maintainer, please bump your package version. If you're a
user, the WireGuard team welcomes any and all feedback on this latest version.
Finally, WireGuard development thrives on donations. By popular demand, we
have a webpage for this: https://www.wireguard.com/donations/
Thank you,
Jason Donenfeld
-----BEGIN PGP SIGNATURE-----
iQJEBAEBCAAuFiEEq5lC5tSkz8NBJiCnSfxwEqXeA64FAmC8lxsQHGphc29uQHp4
MmM0LmNvbQAKCRBJ/HASpd4DrmCUD/oCNMLbpF21NhWXh8gAlfiN2jwoRblm5Ibq
mO1VTLlBLf7Cr7PufHJ5sEWfTeqMoLIDx8XWXZdbgUwfMhPDHcNXITH1n7RQmBQt
A8b2jWUBBqqZipsEL+Sq/EBpMrVtfwNUM1mcuLsQ1j2ol2Mm6vmn42fTVjz4hvD9
NPWlLzHsnwt6q7t4/HiODWtJATXNMP+CxF7GPF5rSLL+zOAFkFSRoMupO0qTUCIi
pCjQoTYD5d5GD/5xVc12uaElYN9AJq7q7J78yAtvZ/BCubHQ80MYwXA5vwQ65sQI
dVLZ1vWPU3r4xe2xLewsvvCq318ojO54Zwn9yld0ZDpAJtgcDA0lb13iWjTh8x9o
Z7IcqUAT66tpZe1FA1YY00T2+SpqQoCNBhiMpUe8dd7Aqy//1N8y64WdGIPF9SGH
+7Eb1X2aaXebacksLbKcfkZbuXwtdExKMpY/ppHceMz3UoacEehf7F1azZmNfo+S
l+Fs6v7fduPpSOetz97HoPsgunjpffs8EfV2XuwBe8dqRXlLs97CHCjGR1ct5jua
ZOAkOh8UErsSGJc+imEQmRysXsqxIcTACAvCnijZ38d65/Tw0twouSW1EMl8yu8i
rG9GVwvwuK+8Aq9me8nXyd3Ik7pUyKtKs2Hs51/ruJQLfgYPt6lqz8k+boEl2rNn
F/yp2xPdtQ==
=JJZr
-----END PGP SIGNATURE-----
reply other threads:[~2021-06-06 9:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1649a9a43f0f2206@lists.zx2c4.com \
--to=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).