mbox series

[next-next,0/4] wireguard patches for 5.20-rc1

Message ID 20220802125613.340848-1-Jason@zx2c4.com (mailing list archive)
Headers show
Series wireguard patches for 5.20-rc1 | expand

Message

Jason A. Donenfeld Aug. 2, 2022, 12:56 p.m. UTC
Hi Jakub,

I had planned to send these out eventually as net.git patches, but as
you emailed earlier, I figure there's no harm in just doing this now for
net-next.git. Please apply the following small fixes:

1) Rather than using msleep() in order to approximate ktime_get_coarse_
   boottime_ns(), instead use an hrtimer, rounded heuristically.

2) An update in selftest config fragments, from Lukas.

3) Linus noticed that a debugging WARN_ON() to detect (impossible) stack
   corruption would still allow the corruption to happen, making it harder
   to get the report about the corruption subsequently.

4) Support for User Mode Linux in the test suite. This depends on some
   UML patches that are slated for 5.20. Richard hasn't sent his pull
   in, but they're in his tree, so I assume it'll happen.

Thanks,
Jason

Jason A. Donenfeld (3):
  wireguard: ratelimiter: use hrtimer in selftest
  wireguard: allowedips: don't corrupt stack when detecting overflow
  wireguard: selftests: support UML

Lukas Bulwahn (1):
  wireguard: selftests: update config fragments

 drivers/net/wireguard/allowedips.c            |  9 ++++---
 drivers/net/wireguard/selftest/allowedips.c   |  6 ++---
 drivers/net/wireguard/selftest/ratelimiter.c  | 25 +++++++++++--------
 kernel/time/hrtimer.c                         |  1 +
 .../testing/selftests/wireguard/qemu/Makefile | 17 ++++++++++++-
 .../selftests/wireguard/qemu/arch/um.config   |  3 +++
 .../selftests/wireguard/qemu/debug.config     |  5 ----
 .../selftests/wireguard/qemu/kernel.config    |  1 -
 8 files changed, 43 insertions(+), 24 deletions(-)
 create mode 100644 tools/testing/selftests/wireguard/qemu/arch/um.config

Comments

Jason A. Donenfeld Aug. 2, 2022, 12:57 p.m. UTC | #1
> [PATCH next-next 0/4] wireguard patches for 5.20-rc1

Grrr... obviously I meant net-next not next-next.

Jason