From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: kuba@kernel.org, pablo@netfilter.org, davem@davemloft.net,
netdev@vger.kernel.org
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>
Subject: [PATCH net 0/3] wireguard patches for 6.0-rc6
Date: Fri, 16 Sep 2022 15:37:37 +0100 [thread overview]
Message-ID: <20220916143740.831881-1-Jason@zx2c4.com> (raw)
Hey guys,
Sorry we didn't get a chance to talk at Plumbers. I saw some of you very
briefly in passing but never had the opportunity to chat. Next time, I
hope.
Please pull the following fixes:
1) The ratelimiter timing test doesn't help outside of development, yet
it is currently preventing the module from being inserted on some
kernels when it flakes at insertion time. So we disable it.
2) A fix for a build error on UML, caused by a recent change in a
different tree.
3) A WARN_ON() is triggered by Kees' new fortified memcpy() patch, due
to memcpy()ing over a sockaddr pointer with the size of a
sockaddr_in[6]. The type safe fix is pretty simple. Given how classic
of a thing sockaddr punning is, I suspect this may be the first in a
few patches like this throughout the net tree, once Kees' fortify
series is more widely deployed (current it's just in next).
Thanks,
Jason
Jason A. Donenfeld (3):
wireguard: ratelimiter: disable timings test by default
wireguard: selftests: do not install headers on UML
wireguard: netlink: avoid variable-sized memcpy on sockaddr
drivers/net/wireguard/netlink.c | 13 +++++-----
drivers/net/wireguard/selftest/ratelimiter.c | 25 ++++++++-----------
.../testing/selftests/wireguard/qemu/Makefile | 2 ++
3 files changed, 18 insertions(+), 22 deletions(-)
--
2.37.3
next reply other threads:[~2022-09-16 14:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 14:37 Jason A. Donenfeld [this message]
2022-09-16 14:37 ` [PATCH net 1/3] wireguard: ratelimiter: disable timings test by default Jason A. Donenfeld
2022-09-16 14:37 ` [PATCH net 2/3] wireguard: selftests: do not install headers on UML Jason A. Donenfeld
2022-09-16 14:37 ` [PATCH net 3/3] wireguard: netlink: avoid variable-sized memcpy on sockaddr Jason A. Donenfeld
2022-09-16 15:02 ` Kees Cook
2022-09-16 15:04 ` Kees Cook
2022-09-20 1:20 ` [PATCH net 0/3] wireguard patches for 6.0-rc6 Jakub Kicinski
2022-09-20 6:47 ` 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=20220916143740.831881-1-Jason@zx2c4.com \
--to=jason@zx2c4.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pablo@netfilter.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).