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 v0.0.20200105 released
Date: Sun, 05 Jan 2020 18:07:57 -0500
Message-ID: <fa073f1fc3e6150b@frisell.zx2c4.com> (raw)

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

Hello,

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

Please note that until Linux 5.6 is released, this snapshot is a
snapshot rather than a secure final release.

== Changes ==

  * qemu: bump packages and support m68k properly
  * qemu: re-add dependency on wireguard sources
  * qemu: only compare archs when deciding whether to use kvm
  
  Our test suite continues to grow. Check out the tremendous set of
  architectures we're now building on https://www.wireguard.com/build-status/
  
  * socket: mark skbs as not on list when receiving via gro
  
  The real purpose of this release. Certain drivers will pass gro skbs to udp,
  at which point the udp driver simply iterates through them and passes them off
  to encap_rcv, which is where we pick up. At the moment, we're not attempting
  to coalesce these into bundles, but we also don't want to wind up having
  cascaded lists of skbs treated separately. The right behavior here, then, is
  to just mark each incoming one as not on a list. This can be seen in practice,
  for example, with Qualcomm's rmnet_perf driver. This lead to crashes on
  OnePlus devices and possibly other Qualcomm 4.14 devices. But I fear that it
  could lead to issues on other drivers on fancy servers, too.
  
  This commit is upstream in net-next as:
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=736775d06bac60d7a353e405398b48b2bd8b1e54

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 snapshot is available in compressed tarball form here:
  https://git.zx2c4.com/wireguard-linux-compat/snapshot/wireguard-linux-compat-0.0.20200105.tar.xz
  SHA2-256: 9f12f68e96f6865325995c38213e09b05751cd1ef03e0bbc9f1bdc3e5680b337

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

iQJEBAEBCAAuFiEEq5lC5tSkz8NBJiCnSfxwEqXeA64FAl4SbDsQHGphc29uQHp4
MmM0LmNvbQAKCRBJ/HASpd4DriGLD/96FFOMidCpQ0bEys1GMJem1V0USzAdllmg
E9NVOakNF4Tj794w0YWWiBVjEkTjojvILMPkQwaCbVpzXd67Elh44MMyfng2LFh5
kpLPrEDWDMcDr1pEZrpANwcueIUNRbe4+/lfnTnhN+Gr5Z10hpiAr4TasAZVJsZ6
dFmTsvf06nqlPfnevWB/H8Vmif4p7QdeKPquOxE4slPBwCNatUa7uJw3kPhstOCi
lp+A+i/oorxb4nwC9y7vIhKeDThWm3NadMLFjj8pn8Lzq4p37VpBUnpHSc0BX6+m
oW7lMa3X7UcQNnNTt1X5PWPI31ajF60H1mfcccuxeH5xpK7+uqa78YuyHRVccpMm
aTf1JGX/+QGxF4hXM7Hp94uPLToMvkcm+w7O9mI80FAXK+sxjdPF7jT3Rl9TfqA4
W/shg40lGr0h7YrVojBwYSA2aF+UgqXX2/U9o3rgkdUAQQ3kRxsZ1bH164GtQvsD
YWt5JzOBFvHboyZnPtJdSlUU1dEuLJJE/PCzY2o+Fxeh8k0fd7VD0TL+mZjR5cLM
00tAaBjqmbcDZRJmnmI4TM2Ebxuai4WeOrVXUebNrCvW/Ec+/JYvCBPqfSbfJjNE
Iu+AZF0VC+H1/TyTgfTiukf2A8vK6zqbjY8ZgVrTDCZ3jactvvDsm0Ggs+16S+7a
hLAESASlbQ==
=LS5o
-----END PGP SIGNATURE-----
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

                 reply index

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publically 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=fa073f1fc3e6150b@frisell.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