WireGuard Archive on lore.kernel.org
 help / color / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "WireGuard mailing list" <wireguard@lists.zx2c4.com>
Subject: [ANNOUNCE] wireguard-linux-compat v1.0.20200520 released
Date: Wed, 20 May 2020 22:40:01 -0600
Message-ID: <5f29b0a4e49519be@mail.zx2c4.com> (raw)

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

Hello,

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

== Changes ==

  This release aligns with the changes I sent to DaveM for 5.7-rc7 and were
  pushed to net.git about 45 minutes ago.
  
  * qemu: use newer iproute2 for gcc-10
  * qemu: add -fcommon for compiling ping with gcc-10
  
  These enable the test suite to compile with gcc-10.
  
  * noise: read preshared key while taking lock
  
  Matt noticed a benign data race when porting the Linux code to OpenBSD.
  
  * queueing: preserve flow hash across packet scrubbing
  * noise: separate receive counter from send counter
  
  WireGuard now works with fq_codel, cake, and other qdiscs that make use of
  skb->hash. This should significantly improve latency spikes related to
  buffer bloat. Here's a before and after graph from some data Toke measured:
  https://data.zx2c4.com/removal-of-buffer-bloat-in-wireguard.png
  
  * compat: support RHEL 8 as 8.2, drop 8.1 support
  * compat: support CentOS 8 explicitly
  * compat: RHEL7 backported the skb hash renamings
  
  The usual RHEL churn.
  
  * compat: backport renamed/missing skb hash members
  
  The new support for fq_codel and friends meant more backporting work.
  
  * compat: ip6_dst_lookup_flow was backported to 4.14, 4.9, and 4.4
  
  The main motivation for releasing this now: three stable kernels were released
  at the same time, with a patch that necessitated updating in our compat layer.

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.20200520.tar.xz
  SHA2-256: 16e7ae4bef734b243428eea07f3b3c3d4721880c3ea8eb8f98628fd6ae5b77c3

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

iQJEBAEBCAAuFiEEq5lC5tSkz8NBJiCnSfxwEqXeA64FAl7GBgoQHGphc29uQHp4
MmM0LmNvbQAKCRBJ/HASpd4DrlKZEACPH+a9eZpo7+wsXdSGph4F9yVN5NxwpxNM
l/ymAzh0ttuoQMYjL8lcU7YSaXYO0LijGooIsUzp/42ex8tawsrOeOkrbMbHW4Gs
nhLxQpoFMSDnGDuVXpPJ44xjdakyB6WfsbqpAgT2Eopzr0bn8Wi2lYxI8Oj8xbE/
g7tjHkV0HwAbetbDsnzy+SrWhKG5mZFL9ZX5dcR1NiaYvFGKoKF2hWlQwxMFQCMs
53Cjfsc0iiZ2D+eHKiIqclju/aRcwJZdmgrjSA8kGqggbdSCSin81rvEEhbDauri
uchnqcNE8DdRDyQP0/jeRVxz1OZw6yc0BLbvERh5ppCqFZFQTFfRCSttrmelgCKU
yCp501Zz5aJsRNsBpyhatFQkLuUmqZJOTZl5g25HdXYMK5Xt6kd9mO6Fyyz8ENcP
Egses+nB9udkO51t6AboBc4OMpu1v8/EVDX+/JJaCXjG22UVYEnHLsNVBJdCnqbD
8ccgWx2alrUZ/tBOl/vISbTwdMSca6VOa1Mvmg05B4EKdioF2qVqgH+58Pt0jTBT
j9YbuG9jeh93DVZmTY9R/vaPDlMKlg8/uzQJQhchpDUOZjWBtB6n17h+y8ySq5dM
QgZbgcHgYqxBzX8Q0fUyT2TrZlcYTfw5+kAbJktxbWS4/+tS0tac+J9YgDwhPmsL
eLHfHZSN5A==
=MZPt
-----END PGP SIGNATURE-----

                 reply index

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=5f29b0a4e49519be@mail.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

WireGuard Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/wireguard/0 wireguard/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 wireguard wireguard/ https://lore.kernel.org/wireguard \
		wireguard@lists.zx2c4.com
	public-inbox-index wireguard

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/com.zx2c4.lists.wireguard


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git