From: Greg KH <gregkh@linuxfoundation.org>
To: Amit Klein <aksecurity@gmail.com>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
edumazet@google.com, w@1wt.eu, davem@davemloft.net,
netdev@vger.kernel.org
Subject: Re: [PATCH 4.9] inet: use bigger hash table for IP ID generation (backported to 4.9 and 4.4)
Date: Tue, 22 Jun 2021 12:35:01 +0200 [thread overview]
Message-ID: <YNG81UEPz3/ajF45@kroah.com> (raw)
In-Reply-To: <60d1a5e9.1c69fb81.7f729.b892@mx.google.com>
On Tue, Jun 22, 2021 at 01:57:13AM -0700, Amit Klein wrote:
> Subject: inet: use bigger hash table for IP ID generation (backported to 4.9 and 4.4)
> From: Amit Klein <aksecurity@gmail.com>
>
> [ Upstream commit aa6dd211e4b1dde9d5dc25d699d35f789ae7eeba ]
>
> This is a backport to 4.9 and 4.4 of the following patch, originally
> developed by Eric Dumazet.
That worked, now queued up, thanks!
greg k-h
prev parent reply other threads:[~2021-06-22 10:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 8:57 [PATCH 4.9] inet: use bigger hash table for IP ID generation (backported to 4.9 and 4.4) Amit Klein
2021-06-22 10:35 ` Greg KH [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=YNG81UEPz3/ajF45@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=aksecurity@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.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