From: David Miller <davem@davemloft.net>
To: Jason@zx2c4.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net 0/4] wireguard fixes for 5.7-rc7
Date: Wed, 20 May 2020 20:56:07 -0700 (PDT) [thread overview]
Message-ID: <20200520.205607.2029699296653494061.davem@davemloft.net> (raw)
In-Reply-To: <20200520044930.8131-1-Jason@zx2c4.com>
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
Date: Tue, 19 May 2020 22:49:26 -0600
> Hopefully these are the last fixes for 5.7:
>
> 1) A trivial bump in the selftest harness to support gcc-10.
> build.wireguard.com is still on gcc-9 but I'll probably switch to
> gcc-10 in the coming weeks.
>
> 2) A concurrency fix regarding userspace modifying the pre-shared key at
> the same time as packets are being processed, reported by Matt
> Dunwoodie.
>
> 3) We were previously clearing skb->hash on egress, which broke
> fq_codel, cake, and other things that actually make use of the flow
> hash for queueing, reported by Dave Taht and Toke Høiland-Jørgensen.
>
> 4) A fix for the increased memory usage caused by (3). This can be
> thought of as part of patch (3), but because of the separate
> reasoning and breadth of it I thought made it a bit cleaner to put in
> a standalone commit.
Series applied.
> Fixes (2), (3), and (4) are -stable material.
Queued up for -stable, thanks.
prev parent reply other threads:[~2020-05-21 3:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 4:49 [PATCH net 0/4] wireguard fixes for 5.7-rc7 Jason A. Donenfeld
2020-05-20 4:49 ` [PATCH net 1/4] wireguard: selftests: use newer iproute2 for gcc-10 Jason A. Donenfeld
2020-05-20 4:49 ` [PATCH net 2/4] wireguard: noise: read preshared key while taking lock Jason A. Donenfeld
2020-05-20 4:49 ` [PATCH net 3/4] wireguard: queueing: preserve flow hash across packet scrubbing Jason A. Donenfeld
2020-05-20 4:49 ` [PATCH net 4/4] wireguard: noise: separate receive counter from send counter Jason A. Donenfeld
2020-05-21 3:56 ` 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=20200520.205607.2029699296653494061.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 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).