netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: holt@sgi.com
Cc: w@1wt.eu, linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	linux-sctp@vger.kernel.org, kuznet@ms2.inr.ac.ru,
	pekkas@netcore.fi, jmorris@namei.org, yoshfuji@linux-ipv6.org,
	kaber@trash.net, vladislav.yasevich@hp.com, sri@us.ibm.com
Subject: Re: [Patch] Limit sysctl_tcp_mem and sysctl_udp_mem initializers to prevent integer overflows.
Date: Sun, 24 Oct 2010 15:28:30 -0700 (PDT)	[thread overview]
Message-ID: <20101024.152830.102557040.davem@davemloft.net> (raw)
In-Reply-To: <20101020120345.436404838@gulag1.americas.sgi.com>

From: Robin Holt <holt@sgi.com>
Date: Wed, 20 Oct 2010 07:03:37 -0500

> Subject: [Patch] Limit sysctl_tcp_mem and sysctl_udp_mem initializers to prevent integer overflows.
> 
> On a 16TB x86_64 machine, sysctl_tcp_mem[2], sysctl_udp_mem[2], and
> sysctl_sctp_mem[2] can integer overflow.  Set limit such that they are
> maximized without overflowing.
> 
> Signed-off-by: Robin Holt <holt@sgi.com>

I'll queue this up for -stable, thanks Robin!

  reply	other threads:[~2010-10-24 22:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20101020120336.967805943@gulag1.americas.sgi.com>
2010-10-20 12:03 ` [Patch] Limit sysctl_tcp_mem and sysctl_udp_mem initializers to prevent integer overflows Robin Holt
2010-10-24 22:28   ` David Miller [this message]
     [not found] <20101002112405.951704198@gulag1.americas.sgi.com>
2010-10-02 11:24 ` Robin Holt
2010-10-02 13:22   ` Eric Dumazet
2010-10-03 11:16     ` Robin Holt
2010-10-05 21:50     ` David Miller
2010-11-10  6:15       ` Robin Holt
2010-10-05 21:50   ` David Miller
2010-10-18 17:43     ` Robin Holt
2010-10-18 17:52       ` Eric Dumazet
2010-10-18 18:34         ` Robin Holt

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=20101024.152830.102557040.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=holt@sgi.com \
    --cc=jmorris@namei.org \
    --cc=kaber@trash.net \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sctp@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pekkas@netcore.fi \
    --cc=sri@us.ibm.com \
    --cc=vladislav.yasevich@hp.com \
    --cc=w@1wt.eu \
    --cc=yoshfuji@linux-ipv6.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).