From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: davem@davemloft.net, netdev@vger.kernel.org
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>
Subject: [PATCH net 0/3] wireguard fixes for 5.6-rc2
Date: Fri, 14 Feb 2020 14:34:01 +0100 [thread overview]
Message-ID: <20200214133404.30643-1-Jason@zx2c4.com> (raw)
Here are three fixes for wireguard collected since rc1:
1) Some small cleanups to the test suite to help massively parallel
builds.
2) A change in how we reset our load calculation to avoid a more
expensive comparison, suggested by Matt Dunwoodie.
3) I've been loading more and more of wireguard's surface into
syzkaller, trying to get our coverage as complete as possible,
leading in this case to a fix for mtu=0 devices.
Jason A. Donenfeld (3):
wireguard: selftests: reduce complexity and fix make races
wireguard: receive: reset last_under_load to zero
wireguard: send: account for mtu=0 devices
drivers/net/wireguard/device.c | 7 ++--
drivers/net/wireguard/receive.c | 7 +++-
drivers/net/wireguard/send.c | 3 +-
.../testing/selftests/wireguard/qemu/Makefile | 38 +++++++------------
4 files changed, 25 insertions(+), 30 deletions(-)
--
2.25.0
next reply other threads:[~2020-02-14 13:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 13:34 Jason A. Donenfeld [this message]
2020-02-14 13:34 ` [PATCH net 1/3] wireguard: selftests: reduce complexity and fix make races Jason A. Donenfeld
2020-02-14 13:34 ` [PATCH net 2/3] wireguard: receive: reset last_under_load to zero Jason A. Donenfeld
2020-02-14 13:34 ` [PATCH net 3/3] wireguard: send: account for mtu=0 devices Jason A. Donenfeld
2020-02-14 15:18 ` Eric Dumazet
2020-02-14 15:56 ` Jason A. Donenfeld
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=20200214133404.30643-1-Jason@zx2c4.com \
--to=jason@zx2c4.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
/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).