From: Fan Du <fan.du@intel.com>
To: johnwheffner@gmail.com
Cc: davem@davemloft.net, netdev@vger.kernel.org, fengyuleidian0615@gmail.com
Subject: [PATCH net-next 4/4] ipv4: clamp sysctl_tcp_probe_threshold
Date: Tue, 10 Mar 2015 17:16:26 +0800 [thread overview]
Message-ID: <1425978986-8512-5-git-send-email-fan.du@intel.com> (raw)
In-Reply-To: <1425978986-8512-1-git-send-email-fan.du@intel.com>
Signed-off-by: Fan Du <fan.du@intel.com>
---
net/ipv4/tcp_output.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/net/ipv4/tcp_output.c b/net/ipv4/tcp_output.c
index 89d3f84..dc0221b 100644
--- a/net/ipv4/tcp_output.c
+++ b/net/ipv4/tcp_output.c
@@ -1900,7 +1900,7 @@ static int tcp_mtu_probe(struct sock *sk)
* probing process by not resetting search range to its orignal.
*/
if (probe_size > tcp_mtu_to_mss(sk, icsk->icsk_mtup.search_high) ||
- interval < net->ipv4.sysctl_tcp_probe_threshold) {
+ interval < max(1, net->ipv4.sysctl_tcp_probe_threshold)) {
/* Check whether enough time has elaplased for
* another round of probing.
*/
--
1.7.1
prev parent reply other threads:[~2015-03-10 9:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 9:16 [PATCH net-next 0/4] Fix for TCP PMTU Fan Du
2015-03-10 9:16 ` [PATCH net-next 1/4] ipv4: Rename tcp_mtu_probing to tcp_blackhole_probe Fan Du
2015-03-10 9:16 ` [PATCH net-next 2/4] ipv4: Correct two conditions checking when buildig nskb Fan Du
2015-03-18 12:44 ` John Heffner
2015-03-10 9:16 ` [PATCH net-next 3/4] ipv4: Use probe_size to check write queue data length Fan Du
2015-03-10 12:26 ` John Heffner
2015-03-18 1:37 ` Fan Du
2015-03-18 12:41 ` John Heffner
2015-03-10 9:16 ` Fan Du [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=1425978986-8512-5-git-send-email-fan.du@intel.com \
--to=fan.du@intel.com \
--cc=davem@davemloft.net \
--cc=fengyuleidian0615@gmail.com \
--cc=johnwheffner@gmail.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).