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.20200712 released
Date: Sun, 12 Jul 2020 21:34:12 -0600	[thread overview]
Message-ID: <913e8149b5a5c3a6@mail.zx2c4.com> (raw)

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

Hello,

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

== Changes ==

  This release brings parity with the commits Linus released a few hours
  ago into 5.8-rc5.
  
  * receive: account for napi_gro_receive never returning GRO_DROP
  
  The napi_gro_receive function no longer returns GRO_DROP ever, making
  handling GRO_DROP dead code. This commit removes that dead code.
  Further, it's not even clear that device drivers have any business in
  taking action after passing off received packets; that's arguably out of
  their hands.
  
  * compat: rhel 8.3 backported skb_reset_redirect
  
  This works with the latest RHEL 8.3 beta, which isn't yet released,
  and breaks CentOS 8 Stream as a result, but Red Hat is so slow to release
  their kernels to testing that we've got a real issue: we can't support
  Red Hat development efforts internally at the same time as supporting
  CentOS 8 Stream, making the stream project something of bust,
  unfortuantely.
  
  * compat: SUSE 15.1 is the final SUSE we need to support
  
  >=15.2 is in SUSE's kernel now. We'll be dropping 15.1 support in a
  few weeks after people have had time to upgrade.
  
  * device: implement header_ops->parse_protocol for AF_PACKET
  
  WireGuard uses skb->protocol to determine packet type, and bails out if
  it's not set or set to something it's not expecting. For AF_PACKET
  injection, we need to support its call chain of:
  
      packet_sendmsg -> packet_snd -> packet_parse_headers ->
        dev_parse_header_protocol -> parse_protocol
  
  Without a valid parse_protocol, this returns zero, and wireguard then
  rejects the skb. So, this wires up the ip_tunnel handler for layer 3
  packets for that case.
  
  * queueing: make use of ip_tunnel_parse_protocol
  
  Now that wg_examine_packet_protocol has been added for general
  consumption as ip_tunnel_parse_protocol, it's possible to remove
  wg_examine_packet_protocol and simply use the new
  ip_tunnel_parse_protocol function directly.
  
  * compat: backport ip_tunnel_parse_protocol and ip_tunnel_header_ops
  
  These are required for moving wg_examine_packet_protocol out of
  wireguard and into upstream.

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.20200712.tar.xz
  SHA2-256: e15b3d4eb2cf186920a6ed13685187d6b846e59eb383c291913628682965ac95

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

iQJEBAEBCAAuFiEEq5lC5tSkz8NBJiCnSfxwEqXeA64FAl8L1i8QHGphc29uQHp4
MmM0LmNvbQAKCRBJ/HASpd4DrnFzD/43H09uMYK2PXPChfizkbiz84SvpWpPMqDn
3frC+9Ijp9icZB3Ksd9qauaQhREle6McSjpFPXVL7n6YlLhYPjE5RodGG/sW60QW
OOsCCWrKu1ict8WDDs0X7dIAtj/kKNwu7dUlJnWJRj3Mwe3Wk7s2/uBurf2X6rvC
IzTGvcDDZ/TNDujhJZFgVRmgMQPXGlH0RIp4LVxJSsAIKO1RhjVGGbaTe2deh8sY
YGcdBbtqOCb3K7X/fH2Lt4Ob2FbaqD+DRNDXdV7hPRo/QYtEMBsiiJsw+R9AqtEv
MCg2EBF7l5T4pTiShZKVJnGYQp69vG94QZBrlMNoVJldtqs9DrwehzXaLG4XWILN
Nn0ja2ZIjni+LpVJy7upYwZ9Fzdv6Q85HMVYJpcErhbbEC6uzln6WjXNGKNy7/oA
l9vLu3uFzAvvXBInZDbpg/YpTvd4cXZ1pFFAAGjwCW9B7C4NIu6na8NT9Q51q9EH
0q7l0Hj/CkL0frC0O1xDd5fYrI6SiZRdlHNVWdBCb7siUSw4yjA1L0x5VGkdKCHX
seZLwUin+gaHUQIvTwzbDuHE77K406P4Xp1x1UBFv6g63uZBY3XKukdZSMBOPrDH
eaEbos+pyyV1R49J+SbMMUHkGhIk70OAoFmq+aHdDqITrmhVH/VjSCM04/IdACqo
V4AllFQlQQ==
=rjkE
-----END PGP SIGNATURE-----

             reply	other threads:[~2020-07-13  3:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-13  3:34 Jason A. Donenfeld [this message]
2020-07-13  4:06 ` Jason A. Donenfeld
2020-07-13  5:19   ` Luca Beltrame
2020-07-13 14:39   ` Samu Voutilainen

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=913e8149b5a5c3a6@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
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).