From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: Sasha Levin <sashal@kernel.org>, stable <stable@vger.kernel.org>,
Willy Tarreau <w@1wt.eu>, Eric Dumazet <edumazet@google.com>,
Amit Klein <aksecurity@gmail.com>
Subject: Re: [stable] Improved TCP source port randomisation
Date: Thu, 23 Jun 2022 18:03:44 +0200 [thread overview]
Message-ID: <YrSO4AO8usZQda1z@kroah.com> (raw)
In-Reply-To: <YrSNqZazgv05N07+@kroah.com>
On Thu, Jun 23, 2022 at 05:58:33PM +0200, Greg Kroah-Hartman wrote:
> On Wed, Jun 22, 2022 at 12:24:19AM +0200, Ben Hutchings wrote:
> > Please pick the following commits for 5.4 and 5.10 stable branches:
> >
> > 90564f36f1c3071d1e0c617cde342f9706e250be tcp: add some entropy in __inet_hash_connect()
> > 506884b616e95714af173c47b89e7d1f5157c190 tcp: use different parts of the port_offset for index and offset
> > dabeb1baad260b2308477991f3006f4a1ac80d6d tcp: add small random increments to the source port
> > 735ad25586cd381a3fdc8283e2d1cd4d65f0e9e7 tcp: dynamically allocate the perturb table used by source ports
> > ada9e93075c7d54a7fd28bae5429ed30ddd89bfa tcp: increase source port perturb table to 2^16
> > 82f233b30b728249d1c374b77d722b2e4f55a631 tcp: drop the hash_32() part from the index calculation
>
> All of these commit ids are not in Linus's tree, are you sure you got
> them correct?
Ah, I can pick them from the mboxes you sent me in the other email...
next prev parent reply other threads:[~2022-06-23 16:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 22:24 [stable] Improved TCP source port randomisation Ben Hutchings
2022-06-23 15:58 ` Greg Kroah-Hartman
2022-06-23 16:03 ` Greg Kroah-Hartman [this message]
2022-06-23 16:48 ` Ben Hutchings
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=YrSO4AO8usZQda1z@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=aksecurity@gmail.com \
--cc=ben@decadent.org.uk \
--cc=edumazet@google.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=w@1wt.eu \
/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