Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "WireGuard mailing list" <wireguard@lists.zx2c4.com>
Subject: [ANNOUNCE] wireguard-linux-compat v1.0.20210219 released
Date: Fri, 19 Feb 2021 15:14:45 +0100	[thread overview]
Message-ID: <5b82970bf3f56fa5@lists.zx2c4.com> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hello,

A new version, v1.0.20210219, of the backported WireGuard kernel module for
3.10 <= Linux <= 5.5.y has been tagged in the git repository.

== Changes ==

  * compat: remove unused version.h headers
  * compat: redefine version constants for sublevel>=256
  * compat: skb_mark_not_on_list will be backported to Ubuntu 18.04
  * compat: zero out skb->cb before icmp
  
  Various compat fixes, most notable of which is that the 4.9.256 and 4.4.256
  kernels no longer cause integer wraparound problems. For more info:
  https://lwn.net/Articles/845120/ https://lwn.net/Articles/845207/
  
  * selftests: test multiple parallel streams
  * qemu: bump default kernel version
  
  Usual test harness improvements.
  
  * peer: put frequently used members above cache lines
  * device: do not generate ICMP for non-IP packets
  * queueing: get rid of per-peer ring buffers
  
  Most notable here is the queueing commit. Having two ring buffers per-peer
  means that every peer resulted in two massive ring allocations. On an 8-core
  x86_64 machine, this commit reduces the per-peer allocation from 18,688 bytes
  to 1,856 bytes, which is an 90% reduction. With some single-machine
  deployments approaching 500,000 peers, we're talking about a reduction from 7
  gigs of memory down to 700 megs of memory.

This release contains commits from: Jason A. Donenfeld and Thadeu Lima de 
Souza Cascardo.

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.20210219.tar.xz
  SHA2-256: 99d35296b8d847a0d4db97a4dda96b464311a6354e75fe0bef6e7c4578690f00

A PGP signature of that file decompressed is available here:
  https://git.zx2c4.com/wireguard-linux-compat/snapshot/wireguard-linux-compat-1.0.20210219.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-----

iQJEBAEBCAAuFiEEq5lC5tSkz8NBJiCnSfxwEqXeA64FAmAvx8IQHGphc29uQHp4
MmM0LmNvbQAKCRBJ/HASpd4DrplOD/9DhOh9/IcW0HtQ1dpY3oiCQQwoSfZNwBsy
84xOTMDs3+/OcTklLJabyryMOMbzOtR9sj0Dlp32PNsIxPEpCrmi4QfjmAT77SnS
+Om4QsQhlzxAAuEdA0ZVlbHdV9+9Lxa1ajn1yHnz0oC2iDWIrMjvascggBBcexX4
9qmJV/bsEjVlI3LYS7WrISeFW9MhEMt1eDkUgGV32UlLDMkHNvexg/fRFaEl5bJL
u95mmY28nqv4MgtP0m5RRcQgWlgp/W3fYBp+ThRvm2rMPV1EjH1ZHphZ9imH7ZUt
w+aXiQHbIzlV0jUKWIVGISsHqT1rHXGhTH0fxQSl8oaa3jNBPj/RDWU1uxGfMJDP
OY5DP5x9RkEjmv6KfZS3aIz2OXgDHOVa/2M9HTo+ye5SLSr0Og374LXAHVvHR+xK
yjkLi5yturusltjbo3iK/0LzUZ6QZt3gc6fzid0ljlg1+QJW332qQCtZAEmeSKzt
xVf8iAapl5ezwN6NZNxTSxuzlVDl0f1c9sgjAjGbVAphziQvrmK9n4Iz52oOyNre
bLe5Al/tUBysnT6yKglODJhr7jrhtOEoaoU5ROEcPswT6QmBUOW2EAMVoQ+AYyp9
vMGQ97Jvew1sNBYmfAUrO1l/Azpfi0Mj3nFtyOGx/mgVPkGqhntWpFol0aImaEPc
7SReRurgMA==
=wGOc
-----END PGP SIGNATURE-----

                 reply	other threads:[~2021-02-19 14:14 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=5b82970bf3f56fa5@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).