From: David Miller <davem@davemloft.net>
To: ffusco@redhat.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next 1/2] neigh: prevent overflowing params in /proc/sys/net/ipv4/neigh/
Date: Fri, 26 Jul 2013 14:22:31 -0700 (PDT) [thread overview]
Message-ID: <20130726.142231.339341472515071199.davem@davemloft.net> (raw)
In-Reply-To: <ceef40ec2f64a50afcfc43375a9306ab0661fdf7.1374654531.git.ffusco@redhat.com>
From: Francesco Fusco <ffusco@redhat.com>
Date: Wed, 24 Jul 2013 10:39:06 +0200
> Without this patch, the fields app_solicit, gc_thresh1, gc_thresh2,
> gc_thresh3, proxy_qlen, ucast_solicit, mcast_solicit could have
> assumed negative values when setting large numbers.
>
> Signed-off-by: Francesco Fusco <ffusco@redhat.com>
Applied.
next prev parent reply other threads:[~2013-07-26 21:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 8:39 [PATCH net-next 0/2] Fix overflow errors in /proc/sys/net/ipv4/neigh/ Francesco Fusco
2013-07-24 8:39 ` [PATCH net-next 1/2] neigh: prevent overflowing params " Francesco Fusco
2013-07-26 21:22 ` David Miller [this message]
2013-07-24 8:39 ` [PATCH net-next 2/2] sysctl: range checking in do_proc_dointvec_ms_jiffies_conv Francesco Fusco
2013-07-24 14:35 ` Sergei Shtylyov
2013-07-26 21:23 ` David Miller
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=20130726.142231.339341472515071199.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ffusco@redhat.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).