linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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.14] inet: use bigger hash table for IP ID generation (backported to 4.14)
Date: Fri, 18 Jun 2021 12:24:36 +0200	[thread overview]
Message-ID: <YMx0ZIAkTloug34m@kroah.com> (raw)
In-Reply-To: <60cc6c9a.1c69fb81.70a57.7034@mx.google.com>

On Fri, Jun 18, 2021 at 02:51:22AM -0700, Amit Klein wrote:
> Subject: inet: use bigger hash table for IP ID generation (backported to 4.14)
> From: Amit Klein <aksecurity@gmail.com>
> 
> This is a backport to 4.14 of the following patch, originally
> developed by Eric Dumazet.
> 
> In commit 73f156a6e8c1 ("inetpeer: get rid of ip_id_count")
> I used a very small hash table that could be abused
> by patient attackers to reveal sensitive information.
> 
> Switch to a dynamic sizing, depending on RAM size.
> 
> Typical big hosts will now use 128x more storage (2 MB)
> to get a similar increase in security and reduction
> of hash collisions.
> 
> As a bonus, use of alloc_large_system_hash() spreads
> allocated memory among all NUMA nodes.
> 
> Fixes: 73f156a6e8c1 ("inetpeer: get rid of ip_id_count")
> Reported-by: Amit Klein <aksecurity@gmail.com>
> Cc: stable@vger.kernel.org
> Cc: Eric Dumazet <edumazet@google.com>
> Cc: Willy Tarreau <w@1wt.eu>
> ---

What is the git commit id of this patch in Linus's tree?

thanks,

greg k-h

  reply	other threads:[~2021-06-18 10:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-18  9:51 [PATCH 4.14] inet: use bigger hash table for IP ID generation (backported to 4.14) Amit Klein
2021-06-18 10:24 ` Greg KH [this message]
2021-06-18 10:29   ` Amit Klein

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=YMx0ZIAkTloug34m@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;
as well as URLs for NNTP newsgroup(s).