All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: Jason@zx2c4.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net 0/5] wireguard fixes for 5.6-rc1
Date: Wed, 05 Feb 2020 14:15:37 +0100 (CET)	[thread overview]
Message-ID: <20200205.141537.74468083994693269.davem@davemloft.net> (raw)
In-Reply-To: <20200204211729.365431-1-Jason@zx2c4.com>

From: "Jason A. Donenfeld" <Jason@zx2c4.com>
Date: Tue,  4 Feb 2020 22:17:24 +0100

> Here are fixes for WireGuard before 5.6-rc1 is tagged. It includes:
> 
> 1) A fix for a UaF (caused by kmalloc failing during a very small
>    allocation) that syzkaller found, from Eric Dumazet.
> 
> 2) A fix for a deadlock that syzkaller found, along with an additional
>    selftest to ensure that the bug fix remains correct, from me.
> 
> 3) Two little fixes/cleanups to the selftests from Krzysztof Kozlowski
>    and me.

Series applied, thanks Jason.

      parent reply	other threads:[~2020-02-05 13:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-04 21:17 [PATCH net 0/5] wireguard fixes for 5.6-rc1 Jason A. Donenfeld
2020-02-04 21:17 ` [PATCH net 1/5] wireguard: allowedips: fix use-after-free in root_remove_peer_lists Jason A. Donenfeld
2020-02-04 21:17   ` Jason A. Donenfeld
2020-02-04 21:17 ` [PATCH net 2/5] wireguard: noise: reject peers with low order public keys Jason A. Donenfeld
2020-02-04 21:17 ` [PATCH net 3/5] wireguard: selftests: ensure non-addition of peers with failed precomputation Jason A. Donenfeld
2020-02-04 21:17 ` [PATCH net 4/5] wireguard: selftests: cleanup CONFIG_ENABLE_WARN_DEPRECATED Jason A. Donenfeld
2020-02-04 21:17 ` [PATCH net 5/5] wireguard: selftests: tie socket waiting to target pid Jason A. Donenfeld
2020-02-05 13:15 ` David Miller [this message]

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=20200205.141537.74468083994693269.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=Jason@zx2c4.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.